cloudstack-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject [1/6] git commit: Fix broken image references.
Date Fri, 10 Aug 2012 00:01:01 GMT
Updated Branches:
  refs/heads/master e7718a909 -> d9864e303

Fix broken image references.


Branch: refs/heads/master
Commit: d9864e303821a814a093f1891c12f27a517f462a
Parents: cdc6cf8
Author: Jessica Tomechak <>
Authored: Thu Aug 9 16:58:15 2012 -0700
Committer: Jessica Tomechak <>
Committed: Thu Aug 9 16:59:41 2012 -0700

 docs/en-US/networking-in-a-pod.xml  |    4 ++--
 docs/en-US/networking-in-a-zone.xml |    4 ++--
 docs/en-US/vm-lifecycle.xml         |    4 ++--
 3 files changed, 6 insertions(+), 6 deletions(-)
diff --git a/docs/en-US/networking-in-a-pod.xml b/docs/en-US/networking-in-a-pod.xml
index 08cf36f..3928715 100644
--- a/docs/en-US/networking-in-a-pod.xml
+++ b/docs/en-US/networking-in-a-pod.xml
@@ -8,9 +8,9 @@
 	<para>Figure 2 illustrates network setup within a single pod. The hosts are connected
to a pod-level switch. At a minimum, the hosts should have one physical uplink to each switch.
Bonded NICs are supported as well. The pod-level switch is a pair of redundant gigabit switches
with 10 G uplinks.</para>
-			<imagedata fileref="./images/.png" />
+			<imagedata fileref="./images/networking-in-a-pod.png" />
-		<textobject><phrase>ReleaseIPButton.png: button to release an IP</phrase></textobject>
+		<textobject><phrase>networking-in-a-pod.png: Network setup in a pod</phrase></textobject>
 	<para>Servers are connected as follows:</para>
diff --git a/docs/en-US/networking-in-a-zone.xml b/docs/en-US/networking-in-a-zone.xml
index 75dba08..e5450bc 100644
--- a/docs/en-US/networking-in-a-zone.xml
+++ b/docs/en-US/networking-in-a-zone.xml
@@ -8,9 +8,9 @@
 	<para>Figure 3 illustrates the network setup within a single zone.</para>
-			<imagedata fileref="./images/.png" />
+			<imagedata fileref="./images/networking-in-a-zone.png" />
-		<textobject><phrase>ReleaseIPButton.png: Depicts network setup in a single
+		<textobject><phrase>networking-in-a-zone.png: Network setup in a single zone</phrase></textobject>
 	<para>A firewall for management traffic operates in the NAT mode. The network typically
is assigned IP addresses in the Class B private address space. Each pod is
assigned IP addresses in the 192.168.*.0/24 Class C private address space.</para>
 	<para>Each zone has its own set of public IP addresses. Public IP addresses from different
zones do not overlap.</para>
diff --git a/docs/en-US/vm-lifecycle.xml b/docs/en-US/vm-lifecycle.xml
index b9b86e7..83e1845 100644
--- a/docs/en-US/vm-lifecycle.xml
+++ b/docs/en-US/vm-lifecycle.xml
@@ -3,9 +3,9 @@
 	<para>Virtual machines can be in the following states:</para>
-			<imagedata fileref="./images/basic_deployment.png" />
+			<imagedata fileref="./images/basic-deployment.png" />
-		<textobject><phrase>basic_deployment.png: Basic two-machine CloudStack deployment</phrase></textobject>
+		<textobject><phrase>basic-deployment.png: Basic two-machine CloudStack deployment</phrase></textobject>
 	<para>Once a virtual machine is destroyed, it cannot be recovered. All the resources
used by the virtual machine will be reclaimed by the system. This includes the virtual machine’s
IP address.</para>
 	<para>A stop will attempt to gracefully shut down the operating system, which typically
involves terminating all the running applications. If the operation system cannot be stopped,
it will be forcefully terminated. This has the same effect as pulling the power cord to a
physical machine.</para>

View raw message