etan39
/
cloudstack
mirror of https://github.com/apache/cloudstack.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Fix broken image references.

This commit is contained in:
Jessica Tomechak 2012-08-09 16:58:15 -07:00
parent cdc6cf8026
commit d9864e3038
3 changed files with 6 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
docs/en-US/networking-in-a-pod.xml
View File

@ -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>

4
docs/en-US/networking-in-a-zone.xml
View File

@ -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>

4
docs/en-US/vm-lifecycle.xml
View File

@ -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>