diff --git a/docs/en-US/Book_Info.xml b/docs/en-US/Book_Info.xml index 155a20bf2fd..6ff42f28bd1 100644 --- a/docs/en-US/Book_Info.xml +++ b/docs/en-US/Book_Info.xml @@ -1,18 +1,37 @@ - %BOOK_ENTITIES; ]> + + + - CloudPlatform (powered by Apache CloudStack) version 3.0.4 Release Notes + &PRODUCT; version 3.0.4 Release Notes Revised June 14, 2012 5:48 pm Pacific - Citrix CloudPlatform 3.0.4 Powered by Apache CloudStack + Citrix &PRODUCT; 3.0.4 Powered by Apache CloudStack 1 - Release notes for patch release of CloudPlatform to support the XenServer patch XS602E003. + Release notes for patch release of &PRODUCT; to support the XenServer patch XS602E003. @@ -24,4 +43,4 @@ - \ No newline at end of file + diff --git a/docs/en-US/basic-zone-configuration.xml b/docs/en-US/basic-zone-configuration.xml index 5c5d176a45e..bbfd6ec4bb5 100644 --- a/docs/en-US/basic-zone-configuration.xml +++ b/docs/en-US/basic-zone-configuration.xml @@ -1,8 +1,27 @@ - %BOOK_ENTITIES; ]> + + +
Basic Zone Configuration @@ -47,7 +66,7 @@ Choose which traffic types will be carried by the physical network. The traffic types are management, public, guest, and storage traffic. For more information about the types, roll over the icons to display their tool tips, or see Basic Zone Network Traffic Types. This screen starts out with some traffic types already assigned. To add more, drag and drop traffic types onto the network. You can also change the network name if desired. - 3. (Introduced in version 3.0.1) Assign a network traffic label to each traffic type on the physical network. These labels must match the labels you have already defined on the hypervisor host. To assign each label, click the Edit button under the traffic type icon. A popup dialog appears where you can type the label, then click OK. + (Introduced in version 3.0.1) Assign a network traffic label to each traffic type on the physical network. These labels must match the labels you have already defined on the hypervisor host. To assign each label, click the Edit button under the traffic type icon. A popup dialog appears where you can type the label, then click OK. These traffic labels will be defined only for the hypervisor selected for the first cluster. For all other hypervisors, the labels can be configured after the zone is created. (VMware only) If you have enabled Nexus dvSwitch in the environment, you must specify the corresponding Ethernet port profile names as network traffic label for each traffic type on the physical network. For more information on Nexus dvSwitch, see Configuring a vSphere Cluster with Nexus 1000v Virtual Switch. @@ -125,4 +144,4 @@ -
\ No newline at end of file + diff --git a/docs/en-US/basic-zone-physical-network-configuration.xml b/docs/en-US/basic-zone-physical-network-configuration.xml index dac86b3a209..a9b8f55fb80 100644 --- a/docs/en-US/basic-zone-physical-network-configuration.xml +++ b/docs/en-US/basic-zone-physical-network-configuration.xml @@ -1,8 +1,27 @@ - %BOOK_ENTITIES; ]> + + +
Basic Zone Physical Network Configuration In a basic network, configuring the physical network is fairly straightforward. You only need to configure one guest network to carry traffic that is generated by guest VMs. When you first add a zone to CloudPlatform, you set up the guest network through the Add Zone screens. diff --git a/docs/en-US/best-practices-for-vms.xml b/docs/en-US/best-practices-for-vms.xml index 000f6766153..59e270864e5 100644 --- a/docs/en-US/best-practices-for-vms.xml +++ b/docs/en-US/best-practices-for-vms.xml @@ -1,6 +1,23 @@ + +
VM Lifecycle The CloudPlatform administrator should monitor the total number of VM instances in each cluster, and disable allocation to the cluster if the total is approaching the maximum that the hypervisor can handle. Be sure to leave a safety margin to allow for the possibility of one or more hosts failing, which would increase the VM load on the other hosts as the VMs are automatically redeployed. Consult the documentation for your chosen hypervisor to find the maximum permitted number of VMs per host, then use CloudPlatform global configuration settings to set this as the default limit. Monitor the VM activity in each cluster at all times. Keep the total number of VMs below a safe level that allows for the occasional host failure. For example, if there are N hosts in the cluster, and you want to allow for one host in the cluster to be down at any given time, the total number of VM instances you can permit in the cluster is at most (N-1) * (per-host-limit). Once a cluster reaches this number of VMs, use the CloudPlatform UI to disable allocation of more VMs to the cluster..
- diff --git a/docs/en-US/best-practices-primary-storage.xml b/docs/en-US/best-practices-primary-storage.xml index 4b4ef9a8f82..c02501bcdb1 100644 --- a/docs/en-US/best-practices-primary-storage.xml +++ b/docs/en-US/best-practices-primary-storage.xml @@ -1,8 +1,27 @@ - %BOOK_ENTITIES; ]> + + +
Best Practices for Primary Storage @@ -10,4 +29,3 @@ Ensure that nothing is stored on the server. Adding the server to CloudPlatform will destroy any existing data
- diff --git a/docs/en-US/best-practices-secondary-storage.xml b/docs/en-US/best-practices-secondary-storage.xml index 27b889d539b..5c08f9dbd1d 100644 --- a/docs/en-US/best-practices-secondary-storage.xml +++ b/docs/en-US/best-practices-secondary-storage.xml @@ -1,8 +1,27 @@ - %BOOK_ENTITIES; ]> + + +
Best Practices for Secondary Storage @@ -11,4 +30,3 @@ Ensure that nothing is stored on the server. Adding the server to CloudPlatform will destroy any existing data.
- diff --git a/docs/en-US/best-practices-templates.xml b/docs/en-US/best-practices-templates.xml index 71bc97be8f1..411ae3a061d 100644 --- a/docs/en-US/best-practices-templates.xml +++ b/docs/en-US/best-practices-templates.xml @@ -1,8 +1,27 @@ - %BOOK_ENTITIES; ]> + + +
Best Practices for Templates If you plan to use large templates (100 GB or larger), be sure you have a 10-gigabit network to support the large templates. A slower network can lead to timeouts and other errors when large templates are used. diff --git a/docs/en-US/best-practices-virtual-router.xml b/docs/en-US/best-practices-virtual-router.xml index 07324e804f1..060d8680992 100644 --- a/docs/en-US/best-practices-virtual-router.xml +++ b/docs/en-US/best-practices-virtual-router.xml @@ -1,12 +1,31 @@ - %BOOK_ENTITIES; ]> + + +
Best Practices for Virtual Routers - WARNING: Restarting a virtual router from a hypervisor console deletes all the iptables rules. To work around this issue, stop the virtual router and start it from the CloudPlatform UI. + WARNING: Restarting a virtual router from a hypervisor console deletes all the iptables rules. To work around this issue, stop the virtual router and start it from the &PRODUCT; UI. WARNING: Do not use the destroyRouter API when only one router is available in the network, because restartNetwork API with the cleanup=false parameter can't recreate it later. If you want to destroy and recreate the single router available in the network, use the restartNetwork API with the cleanup=true parameter.