diff --git a/docs/en-US/Author_Group.xml b/docs/en-US/Author_Group.xml index faccf5e2c1a..ccb615ba0ab 100644 --- a/docs/en-US/Author_Group.xml +++ b/docs/en-US/Author_Group.xml @@ -1,8 +1,27 @@ - %BOOK_ENTITIES; ]> + + + Jessica diff --git a/docs/en-US/about-pods.xml b/docs/en-US/about-pods.xml index 45c4da7e781..2183ed6a505 100644 --- a/docs/en-US/about-pods.xml +++ b/docs/en-US/about-pods.xml @@ -1,9 +1,28 @@ - %BOOK_ENTITIES; ]> + + +
About Pods TODO -
\ No newline at end of file + diff --git a/docs/en-US/about-virtual-networks.xml b/docs/en-US/about-virtual-networks.xml index 0273bf43844..2fc6ba9ddd5 100644 --- a/docs/en-US/about-virtual-networks.xml +++ b/docs/en-US/about-virtual-networks.xml @@ -1,11 +1,30 @@ - %BOOK_ENTITIES; ]> + + +
About Virtual Networks - A virtual network is a logical construct that enables multi-tenancy on a single physical network. In CloudPlatform, a virtual network can be shared or isolated. + A virtual network is a logical construct that enables multi-tenancy on a single physical network. In &PRODUCT;, a virtual network can be shared or isolated. XenServer and Maintenance Mode Working with Usage XenServer and Maintenance Mode diff --git a/docs/en-US/about-working-with-vms.xml b/docs/en-US/about-working-with-vms.xml index 11d97c0a1b1..f7f3087de67 100644 --- a/docs/en-US/about-working-with-vms.xml +++ b/docs/en-US/about-working-with-vms.xml @@ -1,15 +1,33 @@ + +
About Working with Virtual Machines - CloudPlatform provides administrators with complete control over the lifecycle of all guest VMs executing in the cloud. CloudPlatform provides several guest management operations for end users and administrators. VMs may be stopped, started, rebooted, and destroyed. - Guest VMs have a name and group. VM names and groups are opaque to CloudPlatform and are available for end users to organize their VMs. Each VM can have three names for use in different contexts. Only two of these names can be controlled by the user: + &PRODUCT; provides administrators with complete control over the lifecycle of all guest VMs executing in the cloud. &PRODUCT; provides several guest management operations for end users and administrators. VMs may be stopped, started, rebooted, and destroyed. + Guest VMs have a name and group. VM names and groups are opaque to &PRODUCT; and are available for end users to organize their VMs. Each VM can have three names for use in different contexts. Only two of these names can be controlled by the user: - Instance name – a unique, immutable ID that is generated by CloudPlatform and can not be modified by the user. This name conforms to the requirements in IETF RFC 1123. - Display name – the name displayed in the CloudPlatform web UI. Can be set by the user. Defaults to instance name. - Name – host name that the DHCP server assigns to the VM. Can be set by the user. Defaults to instance name + Instance name – a unique, immutable ID that is generated by &PRODUCT; and can not be modified by the user. This name conforms to the requirements in IETF RFC 1123. + Display name – the name displayed in the &PRODUCT; web UI. Can be set by the user. Defaults to instance name. + Name – host name that the DHCP server assigns to the VM. Can be set by the user. Defaults to instance name Guest VMs can be configured to be Highly Available (HA). An HA-enabled VM is monitored by the system. If the system detects that the VM is down, it will attempt to restart the VM, possibly on a different host. For more information, see HA-Enabled Virtual Machines on - Each new VM is allocated one public IP address. When the VM is started, CloudPlatform automatically creates a static NAT between this public IP address and the private IP address of the VM. + Each new VM is allocated one public IP address. When the VM is started, &PRODUCT; automatically creates a static NAT between this public IP address and the private IP address of the VM. If elastic IP is in use (with the NetScaler load balancer), the IP address initially allocated to the new VM is not marked as elastic. The user must replace the automatically configured IP with a specifically acquired elastic IP, and set up the static NAT mapping between this new IP and the guest VM’s private IP. The VM’s original IP address is then released and returned to the pool of available public IPs. - CloudPlatform cannot distinguish a guest VM that was shut down by the user (such as with the “shutdown” command in Linux) from a VM that shut down unexpectedly. If an HA-enabled VM is shut down from inside the VM, CloudPlatform will restart it. To shut down an HA-enabled VM, you must go through the CloudPlatform UI or API. + &PRODUCT; cannot distinguish a guest VM that was shut down by the user (such as with the “shutdown” command in Linux) from a VM that shut down unexpectedly. If an HA-enabled VM is shut down from inside the VM, &PRODUCT; will restart it. To shut down an HA-enabled VM, you must go through the &PRODUCT; UI or API.
diff --git a/docs/en-US/accept-membership-invite.xml b/docs/en-US/accept-membership-invite.xml index cb53f7eeb4f..dc59d00af65 100644 --- a/docs/en-US/accept-membership-invite.xml +++ b/docs/en-US/accept-membership-invite.xml @@ -1,16 +1,35 @@ - %BOOK_ENTITIES; ]> + + +
Accepting a Membership Invitation - If you have received an invitation to join a CloudPlatform project, and you want to accept the invitation, follow these steps: + If you have received an invitation to join a &PRODUCT; project, and you want to accept the invitation, follow these steps: - Log in to the CloudPlatform UI. + Log in to the &PRODUCT; UI. In the left navigation, click Projects. In Select View, choose Invitations. - If you see the invitation listed onscreen, click the Accept button. Invitations listed on screen were sent to you using your CloudPlatform account name. + If you see the invitation listed onscreen, click the Accept button. Invitations listed on screen were sent to you using your &PRODUCT; account name. If you received an email invitation, click the Enter Token button, and provide the project ID and unique ID code (token) from the email.
diff --git a/docs/en-US/accessing-vms.xml b/docs/en-US/accessing-vms.xml index 47089e0a4d8..7058716ad2e 100644 --- a/docs/en-US/accessing-vms.xml +++ b/docs/en-US/accessing-vms.xml @@ -1,16 +1,34 @@ + +
Accessing VMs Any user can access their own virtual machines. The administrator can access all VMs running in the cloud. - To access a VM through the CloudPlatform UI: + To access a VM through the &PRODUCT; UI: - Log in to the CloudPlatform UI as a user or admin. + Log in to the &PRODUCT; UI as a user or admin. Click Instances, then click the name of a running VM. Click the View Console button . To access a VM directly over the network: The VM must have some port open to incoming traffic. For example, in a basic zone, a new VM might be assigned to a security group which allows incoming traffic. This depends on what security group you picked when creating the VM. In other cases, you can open a port by setting up a port forwarding policy. See IP Forwarding and Firewalling. - If a port is open but you can not access the VM using ssh, it’s possible that ssh is not already enabled on the VM. This will depend on whether ssh is enabled in the template you picked when creating the VM. Access the VM through the CloudPlatform UI and enable ssh on the machine using the commands for the VM’s operating system. + If a port is open but you can not access the VM using ssh, it’s possible that ssh is not already enabled on the VM. This will depend on whether ssh is enabled in the template you picked when creating the VM. Access the VM through the &PRODUCT; UI and enable ssh on the machine using the commands for the VM’s operating system. If the network has an external firewall device, you will need to create a firewall rule to allow access. See IP Forwarding and Firewalling.
diff --git a/docs/en-US/accounts-users-domains.xml b/docs/en-US/accounts-users-domains.xml index b896f3f4b3a..85491295218 100644 --- a/docs/en-US/accounts-users-domains.xml +++ b/docs/en-US/accounts-users-domains.xml @@ -1,8 +1,27 @@ - %BOOK_ENTITIES; ]> + + +
Accounts, Users, and Domains diff --git a/docs/en-US/accounts.xml b/docs/en-US/accounts.xml index 1061ce06813..5292a9ca2f6 100644 --- a/docs/en-US/accounts.xml +++ b/docs/en-US/accounts.xml @@ -1,8 +1,27 @@ - %BOOK_ENTITIES; ]> + + +
diff --git a/docs/en-US/acquire-new-ip-address.xml b/docs/en-US/acquire-new-ip-address.xml index b8df5ed0950..5c02f8abb55 100644 --- a/docs/en-US/acquire-new-ip-address.xml +++ b/docs/en-US/acquire-new-ip-address.xml @@ -1,12 +1,31 @@ - %BOOK_ENTITIES; ]> + + +
Acquiring a New IP Address - Log in to the CloudPlatform UI as an administrator or end user. + Log in to the &PRODUCT; UI as an administrator or end user. In the left navigation, choose Network. Click the name of the network where you want to work with. Click View IP Addresses. diff --git a/docs/en-US/add-additional-guest-network.xml b/docs/en-US/add-additional-guest-network.xml index 76baf448108..e9ddd3327ce 100644 --- a/docs/en-US/add-additional-guest-network.xml +++ b/docs/en-US/add-additional-guest-network.xml @@ -1,12 +1,31 @@ - %BOOK_ENTITIES; ]> + + +
Adding an Additional Guest Network - Log in to the CloudPlatform UI as an administrator or end user. + Log in to the &PRODUCT; UI as an administrator or end user. In the left navigation, choose Network Click Add guest network. Provide the following information: @@ -17,9 +36,8 @@ VLAN ID. The VLAN tag for this network. Gateway. The gateway that the guests should use. Netmask. The netmask in use on the subnet the guests will use. - Start IP/End IP. Enter the first and last IP addresses that define a range that CloudPlatform can assign to guests. We strongly recommend the use of multiple NICs. If multiple NICs are used, they may be in a different subnet. If one NIC is used, these IPs should be in the same CIDR as the pod CIDR. + Start IP/End IP. Enter the first and last IP addresses that define a range that &PRODUCT; can assign to guests. We strongly recommend the use of multiple NICs. If multiple NICs are used, they may be in a different subnet. If one NIC is used, these IPs should be in the same CIDR as the pod CIDR. Click Create.
- diff --git a/docs/en-US/add-ingress-egress-rules.xml b/docs/en-US/add-ingress-egress-rules.xml index 805761e4d7e..4ea072b28e2 100644 --- a/docs/en-US/add-ingress-egress-rules.xml +++ b/docs/en-US/add-ingress-egress-rules.xml @@ -1,39 +1,41 @@ - %BOOK_ENTITIES; ]> + + +
Adding Ingress and Egress Rules to a Security Group - Log in to the CloudPlatform UI as an administrator or end user. + Log in to the &PRODUCT; UI as an administrator or end user. In the left navigation, choose Network In Select view, choose Security Groups, then click the security group you want . To add an ingress rule, click the Ingress Rules tab and fill out the following fields to specify what network traffic is allowed into VM instances in this security group. If no ingress rules are specified, then no traffic will be allowed in, except for responses to any traffic that has been allowed out through an egress rule. - Add by CIDR/Account. Indicate whether the source of the - traffic will be defined by IP address (CIDR) or an existing security group - in a CloudPlatform account (Account). Choose Account if you want to allow - incoming traffic from all VMs in another security group - Protocol. The networking protocol that sources will use to - send traffic to the security group. TCP and UDP are typically used for data - exchange and end-user communications. ICMP is typically used to send error - messages or network monitoring data. - Start Port, End Port. (TCP, UDP only) A range of listening - ports that are the destination for the incoming traffic. If you are opening - a single port, use the same number in both fields. - ICMP Type, ICMP Code. (ICMP only) The type of message and - error code that will be accepted. - CIDR. (Add by CIDR only) To accept only traffic from IP - addresses within a particular address block, enter a CIDR or a - comma-separated list of CIDRs. The CIDR is the base IP address of the - incoming traffic. For example, 192.168.0.0/22. To allow all CIDRs, set to - 0.0.0.0/0. - Account, Security Group. (Add by Account only) To accept only - traffic from another security group, enter the CloudPlatform account and - name of a security group that has already been defined in that account. To - allow traffic between VMs within the security group you are editing now, - enter the same name you used in step 7. + Add by CIDR/Account. Indicate whether the source of the traffic will be defined by IP address (CIDR) or an existing security group in a &PRODUCT; account (Account). Choose Account if you want to allow incoming traffic from all VMs in another security group + Protocol. The networking protocol that sources will use to send traffic to the security group. TCP and UDP are typically used for data exchange and end-user communications. ICMP is typically used to send error messages or network monitoring data. + Start Port, End Port. (TCP, UDP only) A range of listening ports that are the destination for the incoming traffic. If you are opening a single port, use the same number in both fields. + ICMP Type, ICMP Code. (ICMP only) The type of message and error code that will be accepted. + CIDR. (Add by CIDR only) To accept only traffic from IP addresses within a particular address block, enter a CIDR or a comma-separated list of CIDRs. The CIDR is the base IP address of the incoming traffic. For example, 192.168.0.0/22. To allow all CIDRs, set to 0.0.0.0/0. + Account, Security Group. (Add by Account only) To accept only traffic from another security group, enter the &PRODUCT; account and name of a security group that has already been defined in that account. To allow traffic between VMs within the security group you are editing now, enter the same name you used in step 7. The following example allows inbound HTTP access from anywhere: @@ -45,28 +47,12 @@ To add an egress rule, click the Egress Rules tab and fill out the following fields to specify what type of traffic is allowed to be sent out of VM instances in this security group. If no egress rules are specified, then all traffic will be allowed out. Once egress rules are specified, the following types of traffic are allowed out: traffic specified in egress rules; queries to DNS and DHCP servers; and responses to any traffic that has been allowed in through an ingress rule - Add by CIDR/Account. Indicate whether the destination of the - traffic will be defined by IP address (CIDR) or an existing security group - in a CloudPlatform account (Account). Choose Account if you want to allow - outgoing traffic to all VMs in another security group. - Protocol. The networking protocol that VMs will use to send - outgoing traffic. TCP and UDP are typically used for data exchange and - end-user communications. ICMP is typically used to send error messages or - network monitoring data. - Start Port, End Port. (TCP, UDP only) A range of listening - ports that are the destination for the outgoing traffic. If you are opening - a single port, use the same number in both fields. - ICMP Type, ICMP Code. (ICMP only) The type of message and - error code that will be sent - CIDR. (Add by CIDR only) To send traffic only to IP addresses - within a particular address block, enter a CIDR or a comma-separated list of - CIDRs. The CIDR is the base IP address of the destination. For example, - 192.168.0.0/22. To allow all CIDRs, set to 0.0.0.0/0. - Account, Security Group. (Add by Account only) To allow - traffic to be sent to another security group, enter the CloudPlatform - account and name of a security group that has already been defined in that - account. To allow traffic between VMs within the security group you are - editing now, enter its name. + Add by CIDR/Account. Indicate whether the destination of the traffic will be defined by IP address (CIDR) or an existing security group in a &PRODUCT; account (Account). Choose Account if you want to allow outgoing traffic to all VMs in another security group. + Protocol. The networking protocol that VMs will use to send outgoing traffic. TCP and UDP are typically used for data exchange and end-user communications. ICMP is typically used to send error messages or network monitoring data. + Start Port, End Port. (TCP, UDP only) A range of listening ports that are the destination for the outgoing traffic. If you are opening a single port, use the same number in both fields. + ICMP Type, ICMP Code. (ICMP only) The type of message and error code that will be sent + CIDR. (Add by CIDR only) To send traffic only to IP addresses within a particular address block, enter a CIDR or a comma-separated list of CIDRs. The CIDR is the base IP address of the destination. For example, 192.168.0.0/22. To allow all CIDRs, set to 0.0.0.0/0. + Account, Security Group. (Add by Account only) To allow traffic to be sent to another security group, enter the &PRODUCT; account and name of a security group that has already been defined in that account. To allow traffic between VMs within the security group you are editing now, enter its name. Click Add. diff --git a/docs/en-US/add-iso.xml b/docs/en-US/add-iso.xml index 1b6cc411ffa..9376bc75192 100644 --- a/docs/en-US/add-iso.xml +++ b/docs/en-US/add-iso.xml @@ -1,13 +1,32 @@ - %BOOK_ENTITIES; ]> + + +
Adding an ISO To make additional operating system or other software available for use with guest VMs, you can add an ISO. The ISO is typically thought of as an operating system image, but you can also add ISOs for other types of software, such as desktop applications that you want to be installed as part of a template. - Log in to the CloudPlatform UI as an administrator or end user. + Log in to the &PRODUCT; UI as an administrator or end user. In the left navigation bar, click Templates. In Select View, choose ISOs. Click Add ISO. @@ -16,9 +35,9 @@ Name. Short name for the ISO image. (E.g. CentOS 6.2 64 bit). Description. Display test for the ISO image. (E.g. CentOS 6.2 64 bit). URL. The URL that hosts the ISO image. The Management Server must be able to access this location via HTTP. If needed you can place the ISO image directly on the Management Server - Zone. Choose the zone where you want the ISO to be available, or All Zones to make it available throughout CloudPlatform. + Zone. Choose the zone where you want the ISO to be available, or All Zones to make it available throughout &PRODUCT;. Bootable. Whether or not a guest could boot off this ISO image. For example, a CentOS ISO is bootable, a Microsoft Office ISO is not bootable. - OS Type. This helps CloudPlatform and the hypervisor perform certain operations and make assumptions that improve the performance of the guest. Select one of the following. + OS Type. This helps &PRODUCT; and the hypervisor perform certain operations and make assumptions that improve the performance of the guest. Select one of the following. If the operating system of your desired ISO image is listed, choose it. If the OS Type of the ISO is not listed or if the ISO is not bootable, choose Other. @@ -67,8 +86,6 @@ Click OK. The Management Server will download the ISO. Depending on the size of the ISO, this may take a long time. The ISO status column will display Ready once it has been successfully downloaded into secondary storage. Clicking Refresh updates the download percentage. - Important: Wait for the ISO to finish downloading. If you - move on to the next task and try to use the ISO right away, it will appear to fail. - The entire ISO must be available before CloudPlatform can work with it + Important: Wait for the ISO to finish downloading. If you move on to the next task and try to use the ISO right away, it will appear to fail. The entire ISO must be available before &PRODUCT; can work with it
diff --git a/docs/en-US/add-load-balancer-rule.xml b/docs/en-US/add-load-balancer-rule.xml index 99e61a77d73..42895571dbb 100644 --- a/docs/en-US/add-load-balancer-rule.xml +++ b/docs/en-US/add-load-balancer-rule.xml @@ -1,12 +1,31 @@ - %BOOK_ENTITIES; ]> + + +
Adding a Load Balancer Rule - Log in to the CloudPlatform UI as an administrator or end user. + Log in to the &PRODUCT; UI as an administrator or end user. In the left navigation, choose Network. Click the name of the network where you want to load balance the traffic. Click View IP Addresses. @@ -17,7 +36,7 @@ Name. A name for the load balancer rule. Public Port. The port receiving incoming traffic to be balanced. Private Port. The port that the VMs will use to receive the traffic. - Algorithm. Choose the load balancing algorithm you want CloudPlatform to use. CloudPlatform supports a variety of well-known algorithms. If you are not familiar with these choices, you will find plenty of information about them on the Internet. + Algorithm. Choose the load balancing algorithm you want &PRODUCT; to use. &PRODUCT; supports a variety of well-known algorithms. If you are not familiar with these choices, you will find plenty of information about them on the Internet. Stickiness. (Optional) Click Configure and choose the algorithm for the stickiness policy. See Sticky Session Policies for Load Balancer Rules. Click Add VMs, then select two or more VMs that will divide the load of incoming traffic, and click Apply. diff --git a/docs/en-US/add-members-to-projects.xml b/docs/en-US/add-members-to-projects.xml index 94888abc998..a51726e14fc 100644 --- a/docs/en-US/add-members-to-projects.xml +++ b/docs/en-US/add-members-to-projects.xml @@ -1,11 +1,30 @@ - %BOOK_ENTITIES; ]> + + +
Adding Members to a Project - New members can be added to a project by the project’s administrator, the domain administrator of the domain where the project resides or any parent domain, or the CloudPlatform root administrator. There are two ways to add members in CloudPlatform, but only one way is enabled at a time: + New members can be added to a project by the project’s administrator, the domain administrator of the domain where the project resides or any parent domain, or the &PRODUCT; root administrator. There are two ways to add members in &PRODUCT;, but only one way is enabled at a time: If invitations have been enabled, you can send invitations to new members. If invitations are not enabled, you can add members directly through the UI. diff --git a/docs/en-US/add-password-management-to-templates.xml b/docs/en-US/add-password-management-to-templates.xml index 69e16725e9f..05c40afcf10 100644 --- a/docs/en-US/add-password-management-to-templates.xml +++ b/docs/en-US/add-password-management-to-templates.xml @@ -1,12 +1,31 @@ - %BOOK_ENTITIES; ]> + + +
Adding Password Management to Your Templates - CloudPlatform provides an optional password reset feature that allows users to set a temporary admin or root password as well as reset the existing admin or root password from the CloudPlatform UI. - To enable the Reset Password feature, you will need to download an additional script to patch your template. When you later upload the template into CloudPlatform, you can specify whether reset admin/root password feature should be enabled for this template. + &PRODUCT; provides an optional password reset feature that allows users to set a temporary admin or root password as well as reset the existing admin or root password from the &PRODUCT; UI. + To enable the Reset Password feature, you will need to download an additional script to patch your template. When you later upload the template into &PRODUCT;, you can specify whether reset admin/root password feature should be enabled for this template. The password management feature works always resets the account password on instance boot. The script does an HTTP call to the virtual router to retrieve the account password that should be set. As long as the virtual router is accessible the guest will have access to the account password that should be used. When the user requests a password reset the management server generates and sends a new password to the virtual router for the account. Thus an instance reboot is necessary to effect any password changes. If the script is unable to contact the virtual router during instance boot it will not set the password but boot will continue normally. diff --git a/docs/en-US/add-projects-members-from-ui.xml b/docs/en-US/add-projects-members-from-ui.xml index 4ad12063575..670a0ec75ab 100644 --- a/docs/en-US/add-projects-members-from-ui.xml +++ b/docs/en-US/add-projects-members-from-ui.xml @@ -1,13 +1,32 @@ - %BOOK_ENTITIES; ]> + + +
Adding Project Members From the UI The steps below tell how to add a new member to a project if the invitations feature is not enabled in the cloud. If the invitations feature is enabled cloud,as described in , use the procedure in . - Log in to the CloudPlatform UI. + Log in to the &PRODUCT; UI. In the left navigation, click Projects. In Select View, choose Projects. Click the name of the project you want to work with. diff --git a/docs/en-US/add-security-group.xml b/docs/en-US/add-security-group.xml index 2f00b6d47ec..c6ddbf57e82 100644 --- a/docs/en-US/add-security-group.xml +++ b/docs/en-US/add-security-group.xml @@ -1,13 +1,32 @@ - %BOOK_ENTITIES; ]> + + +
Adding a Security Group A user or administrator can change the network offering that is associated with an existing guest network. - Log in to the CloudPlatform UI as an administrator or end user. + Log in to the &PRODUCT; UI as an administrator or end user. In the left navigation, choose Network In Select view, choose Security Groups. Click Add Security Group. diff --git a/docs/en-US/added-API-commands.xml b/docs/en-US/added-API-commands.xml index 7136ad496c8..824eb572856 100644 --- a/docs/en-US/added-API-commands.xml +++ b/docs/en-US/added-API-commands.xml @@ -1,10 +1,28 @@ + +
Added API commands Added in 3.0.3: - enableCiscoNexusVSM (Enables Nexus 1000v dvSwitch in CloudPlatform.) - disableCiscoNexusVSM (Disables Nexus 1000v dvSwitch in CloudPlatform.) - deleteCiscoNexusVSM (Deletes Nexus 1000v dvSwitch in CloudPlatform.) + enableCiscoNexusVSM (Enables Nexus 1000v dvSwitch in &PRODUCT;.) + disableCiscoNexusVSM (Disables Nexus 1000v dvSwitch in &PRODUCT;.) + deleteCiscoNexusVSM (Deletes Nexus 1000v dvSwitch in &PRODUCT;.) listCiscoNexusVSMs (Lists the control VLAN ID, packet VLAN ID, and data VLAN ID, as well as the IP address of the Nexus 1000v dvSwitch.) Added in 3.0.2: @@ -79,7 +97,7 @@ listPhysicalNetworks (Lists physical networks) updatePhysicalNetwork (Updates a physical network) - listSupportedNetworkServices (Lists all network services provided by CloudPlatform or for the given Provider.) + listSupportedNetworkServices (Lists all network services provided by &PRODUCT; or for the given Provider.) addNetworkServiceProvider (Adds a network serviceProvider to a physical network) @@ -140,4 +158,3 @@
- diff --git a/docs/en-US/added-cloudPlatform-error-codes.xml b/docs/en-US/added-cloudPlatform-error-codes.xml index 05ac8833cbb..e3f9b4248ca 100644 --- a/docs/en-US/added-cloudPlatform-error-codes.xml +++ b/docs/en-US/added-cloudPlatform-error-codes.xml @@ -1,6 +1,24 @@ + +
- Added CloudPlatform Error Codes - You can now find the CloudPlatform-specific error code in the exception response for each type of exception. The following list of error codes is added to the new class named CSExceptionErrorCode. These codes are applicable in CloudPlatform 3.0.3 and later versions. + Added &PRODUCT; Error Codes + You can now find the &PRODUCT;-specific error code in the exception response for each type of exception. The following list of error codes is added to the new class named CSExceptionErrorCode. These codes are applicable in &PRODUCT; 3.0.3 and later versions. diff --git a/docs/en-US/adding-IP-addresses-for-the-public-network.xml b/docs/en-US/adding-IP-addresses-for-the-public-network.xml index 50126518ebb..2bc7494db68 100644 --- a/docs/en-US/adding-IP-addresses-for-the-public-network.xml +++ b/docs/en-US/adding-IP-addresses-for-the-public-network.xml @@ -1,11 +1,30 @@ - %BOOK_ENTITIES; ]> + + +
Adding IP Addresses for the Public Network - These instructions assume you have already logged in to the CloudPlatform UI. + These instructions assume you have already logged in to the &PRODUCT; UI. In the left navigation, choose Infrastructure. In Zones, click View More, then click the desired zone . Click the Network tab. diff --git a/docs/en-US/admin-alerts.xml b/docs/en-US/admin-alerts.xml index ebb68c1e36b..4e47032c77a 100644 --- a/docs/en-US/admin-alerts.xml +++ b/docs/en-US/admin-alerts.xml @@ -1,8 +1,27 @@ - %BOOK_ENTITIES; ]> + + +
Administrator Alerts The system provides alerts and events to help with the management of the cloud. Alerts are notices to an administrator, generally delivered by e-mail, notifying the administrator that an error has occurred in the cloud. Alert behavior is configurable. diff --git a/docs/en-US/admin-guide.xml b/docs/en-US/admin-guide.xml index a4fbb425255..c10455d4213 100644 --- a/docs/en-US/admin-guide.xml +++ b/docs/en-US/admin-guide.xml @@ -1,8 +1,27 @@ - %BOOK_ENTITIES; ]> + + + Administrator Guide diff --git a/docs/en-US/advanced-zone-configuration.xml b/docs/en-US/advanced-zone-configuration.xml index cd8a4da0e97..6803888b881 100644 --- a/docs/en-US/advanced-zone-configuration.xml +++ b/docs/en-US/advanced-zone-configuration.xml @@ -1,9 +1,28 @@ - %BOOK_ENTITIES; ]> + + +
Advanced Zone Configuration TODO -
\ No newline at end of file +
diff --git a/docs/en-US/advanced-zone-physical-network-configuration.xml b/docs/en-US/advanced-zone-physical-network-configuration.xml index 73fadec049c..8e1e4456843 100644 --- a/docs/en-US/advanced-zone-physical-network-configuration.xml +++ b/docs/en-US/advanced-zone-physical-network-configuration.xml @@ -1,10 +1,28 @@ - %BOOK_ENTITIES; ]> + + +
Advanced Zone Physical Network Configuration Within a zone that uses advanced networking, you need to tell the Management Server how the physical network is set up to carry different kinds of traffic in isolation. -
diff --git a/docs/en-US/alerts.xml b/docs/en-US/alerts.xml index 81f5f7fbd8b..65f957b5ab5 100644 --- a/docs/en-US/alerts.xml +++ b/docs/en-US/alerts.xml @@ -1,3 +1,21 @@ + +
Alerts The following is the list of alert type numbers. The current alerts can be found by calling listAlerts. diff --git a/docs/en-US/allocators.xml b/docs/en-US/allocators.xml index 99c9e572dd6..d8ce2b8612b 100644 --- a/docs/en-US/allocators.xml +++ b/docs/en-US/allocators.xml @@ -1,9 +1,28 @@ - %BOOK_ENTITIES; ]> + + +
Allocators - CloudPlatform enables administrators to write custom allocators that will choose the Host to place a new guest and the storage host from which to allocate guest virtual disk images. -
\ No newline at end of file + &PRODUCT; enables administrators to write custom allocators that will choose the Host to place a new guest and the storage host from which to allocate guest virtual disk images. +
diff --git a/docs/en-US/api-reference.xml b/docs/en-US/api-reference.xml index c4ca74b3328..74dcbb849cb 100644 --- a/docs/en-US/api-reference.xml +++ b/docs/en-US/api-reference.xml @@ -1,3 +1,21 @@ + +
API Reference Documentation 2.2 API Reference: diff --git a/docs/en-US/appendix-a-time-zones.xml b/docs/en-US/appendix-a-time-zones.xml index 8cd904efede..83648ca3c05 100644 --- a/docs/en-US/appendix-a-time-zones.xml +++ b/docs/en-US/appendix-a-time-zones.xml @@ -1,11 +1,30 @@ - %BOOK_ENTITIES; ]> + + +
Appendix A—Time Zones - The following time zone identifiers are accepted by CloudPlatform. There are several places that have a time zone as a required or optional parameter. These include scheduling recurring snapshots, creating a user, and specifying the usage time zone in the Configuration table. + The following time zone identifiers are accepted by &PRODUCT;. There are several places that have a time zone as a required or optional parameter. These include scheduling recurring snapshots, creating a user, and specifying the usage time zone in the Configuration table. diff --git a/docs/en-US/asynchronous-commands-example.xml b/docs/en-US/asynchronous-commands-example.xml index 3bc65b66dd8..be72997143d 100644 --- a/docs/en-US/asynchronous-commands-example.xml +++ b/docs/en-US/asynchronous-commands-example.xml @@ -1,3 +1,21 @@ + +
Example @@ -85,4 +103,4 @@ <jobresult>Unable to deploy virtual machine id = 100 due to not enough capacity</jobresult> </queryasyncjobresult> -
\ No newline at end of file +
diff --git a/docs/en-US/asynchronous-commands.xml b/docs/en-US/asynchronous-commands.xml index 8a6255b3387..b0a86b6a374 100644 --- a/docs/en-US/asynchronous-commands.xml +++ b/docs/en-US/asynchronous-commands.xml @@ -1,6 +1,24 @@ + +
Asynchronous Commands - Starting in CloudStack 2.x, the notion of asynchronous commands has been introduced. Commands are designated as asynchronous when they can potentially take a long period of time to complete such as creating a snapshot or disk volume. They differ from synchronous commands by the following: + Asynchronous commands were introduced in &PRODUCT; 2.x. Commands are designated as asynchronous when they can potentially take a long period of time to complete such as creating a snapshot or disk volume. They differ from synchronous commands by the following: They are identified in the API Reference by an (A). @@ -12,4 +30,3 @@
- diff --git a/docs/en-US/attach-iso-to-vm.xml b/docs/en-US/attach-iso-to-vm.xml index 4db9db0dd17..b5cc177b76b 100644 --- a/docs/en-US/attach-iso-to-vm.xml +++ b/docs/en-US/attach-iso-to-vm.xml @@ -1,8 +1,27 @@ - %BOOK_ENTITIES; ]> + + +
Attaching an ISO to a VM diff --git a/docs/en-US/attaching-volume.xml b/docs/en-US/attaching-volume.xml index e818a474188..c65337a6479 100644 --- a/docs/en-US/attaching-volume.xml +++ b/docs/en-US/attaching-volume.xml @@ -1,13 +1,32 @@ - %BOOK_ENTITIES; ]> + + +
Attaching a Volume You can attach a volume to a guest VM to provide extra disk storage. Attach a volume when you first create a new volume, when you are moving an existing volume from one VM to another, or after you have migrated a volume from one storage pool to another. - Log in to the CloudPlatform UI as a user or admin. + Log in to the &PRODUCT; UI as a user or admin. In the left navigation, click Storage. In Select View, choose Volumes. 4. Click the volume name in the Volumes list, then click the Attach Disk button @@ -22,4 +41,3 @@ When the volume has been attached, you should be able to see it by clicking Instances, the instance name, and View Volumes.
- diff --git a/docs/en-US/automatic-snapshot-creation-retention.xml b/docs/en-US/automatic-snapshot-creation-retention.xml index 9bf6b34d9f6..cd013143586 100644 --- a/docs/en-US/automatic-snapshot-creation-retention.xml +++ b/docs/en-US/automatic-snapshot-creation-retention.xml @@ -1,18 +1,30 @@ - %BOOK_ENTITIES; ]> + + +
Automatic Snapshot Creation and Retention - (Supported for the following hypervisors: XenServer, - VMware vSphere, and KVM) + (Supported for the following hypervisors: XenServer, VMware vSphere, and KVM) Users can set up a recurring snapshot policy to automatically create multiple snapshots of a disk at regular intervals. Snapshots can be created on an hourly, daily, weekly, or monthly interval. One snapshot policy can be set up per disk volume. For example, a user can set up a daily snapshot at 02:30. - With each snapshot schedule, users can also specify the number of scheduled snapshots to be - retained. Older snapshots that exceed the retention limit are automatically deleted. This - user-defined limit must be equal to or lower than the global limit set by the CloudPlatform - administrator. See . The limit applies only to - those snapshots that are taken as part of an automatic recurring snapshot policy. Additional - manual snapshots can be created and retained. + With each snapshot schedule, users can also specify the number of scheduled snapshots to be retained. Older snapshots that exceed the retention limit are automatically deleted. This user-defined limit must be equal to or lower than the global limit set by the &PRODUCT; administrator. See . The limit applies only to those snapshots that are taken as part of an automatic recurring snapshot policy. Additional manual snapshots can be created and retained.