Updated Branches: refs/heads/master e7718a909 -> d9864e303
Fix broken image references. Project: http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/repo Commit: http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/commit/d9864e30 Tree: http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/tree/d9864e30 Diff: http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/diff/d9864e30 Branch: refs/heads/master Commit: d9864e303821a814a093f1891c12f27a517f462a Parents: cdc6cf8 Author: Jessica Tomechak <[email protected]> Authored: Thu Aug 9 16:58:15 2012 -0700 Committer: Jessica Tomechak <[email protected]> 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(-) ---------------------------------------------------------------------- http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/d9864e30/docs/en-US/networking-in-a-pod.xml ---------------------------------------------------------------------- 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> <mediaobject> <imageobject> - <imagedata fileref="./images/.png" /> + <imagedata fileref="./images/networking-in-a-pod.png" /> </imageobject> - <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> </mediaobject> <para>Servers are connected as follows:</para> <itemizedlist> http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/d9864e30/docs/en-US/networking-in-a-zone.xml ---------------------------------------------------------------------- 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> <mediaobject> <imageobject> - <imagedata fileref="./images/.png" /> + <imagedata fileref="./images/networking-in-a-zone.png" /> </imageobject> - <textobject><phrase>ReleaseIPButton.png: Depicts network setup in a single zone</phrase></textobject> + <textobject><phrase>networking-in-a-zone.png: Network setup in a single zone</phrase></textobject> </mediaobject> <para>A firewall for management traffic operates in the NAT mode. The network typically is assigned IP addresses in the 192.168.0.0/16 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> http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/d9864e30/docs/en-US/vm-lifecycle.xml ---------------------------------------------------------------------- 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> <mediaobject> <imageobject> - <imagedata fileref="./images/basic_deployment.png" /> + <imagedata fileref="./images/basic-deployment.png" /> </imageobject> - <textobject><phrase>basic_deployment.png: Basic two-machine CloudStack deployment</phrase></textobject> + <textobject><phrase>basic-deployment.png: Basic two-machine CloudStack deployment</phrase></textobject> </mediaobject> <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>
