Return-Path: X-Original-To: apmail-incubator-cloudstack-commits-archive@minotaur.apache.org Delivered-To: apmail-incubator-cloudstack-commits-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 72993D15C for ; Thu, 2 Aug 2012 23:46:01 +0000 (UTC) Received: (qmail 20873 invoked by uid 500); 2 Aug 2012 23:46:01 -0000 Delivered-To: apmail-incubator-cloudstack-commits-archive@incubator.apache.org Received: (qmail 20853 invoked by uid 500); 2 Aug 2012 23:46:01 -0000 Mailing-List: contact cloudstack-commits-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: cloudstack-dev@incubator.apache.org Delivered-To: mailing list cloudstack-commits@incubator.apache.org Received: (qmail 20844 invoked by uid 99); 2 Aug 2012 23:46:01 -0000 Received: from tyr.zones.apache.org (HELO tyr.zones.apache.org) (140.211.11.114) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 02 Aug 2012 23:46:01 +0000 Received: by tyr.zones.apache.org (Postfix, from userid 65534) id D2C121B738; Thu, 2 Aug 2012 23:46:00 +0000 (UTC) Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 8bit From: chipchilders@apache.org To: cloudstack-commits@incubator.apache.org X-Mailer: ASF-Git Admin Mailer Subject: git commit: Patch from Joe Brockmeier - Adding Apache license, DTD fixes, &product; entity and other misc fixes to d-named files under /doc. Message-Id: <20120802234600.D2C121B738@tyr.zones.apache.org> Date: Thu, 2 Aug 2012 23:46:00 +0000 (UTC) Updated Branches: refs/heads/master 95b6a5eed -> c35153cef Patch from Joe Brockmeier - Adding Apache license, DTD fixes, &product; entity and other misc fixes to d-named files under /doc. Project: http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/repo Commit: http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/commit/c35153ce Tree: http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/tree/c35153ce Diff: http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/diff/c35153ce Branch: refs/heads/master Commit: c35153cefd42ddc7b265b36f9ef4886cf947c97c Parents: 95b6a5e Author: Chip Childers Authored: Thu Aug 2 19:44:45 2012 -0400 Committer: Chip Childers Committed: Thu Aug 2 19:44:45 2012 -0400 ---------------------------------------------------------------------- docs/en-US/dates-in-usage-record.xml | 18 +++++++++++ docs/en-US/dedicated-ha-hosts.xml | 25 +++++++++++++-- docs/en-US/default-account-resource-limit.xml | 24 +++++++++++++-- docs/en-US/default-template.xml | 23 +++++++++++++- docs/en-US/delete-templates.xml | 21 ++++++++++++- docs/en-US/deleting-vms.xml | 24 +++++++++++++-- docs/en-US/deployment-architecture-overview.xml | 23 +++++++++++++- docs/en-US/deployment_architecture_overview.xml | 24 +++++++++++++-- docs/en-US/detach-move-volumes.xml | 26 +++++++++++++-- docs/en-US/developer-getting-started.xml | 22 ++++++++++++- docs/en-US/developer-guide.xml | 21 ++++++++++++- docs/en-US/developer-introduction.xml | 21 ++++++++++++- docs/en-US/developer_guide.xml | 21 ++++++++++++- docs/en-US/disable-enable-zones-pods-clusters.xml | 23 +++++++++++++- docs/en-US/disk-volume-usage-record-format.xml | 19 +++++++++++- docs/en-US/dns-dhcp.xml | 21 ++++++++++++- docs/en-US/domains.xml | 22 ++++++++++++- 17 files changed, 346 insertions(+), 32 deletions(-) ---------------------------------------------------------------------- http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/c35153ce/docs/en-US/dates-in-usage-record.xml ---------------------------------------------------------------------- diff --git a/docs/en-US/dates-in-usage-record.xml b/docs/en-US/dates-in-usage-record.xml index ff46587..0fe430d 100644 --- a/docs/en-US/dates-in-usage-record.xml +++ b/docs/en-US/dates-in-usage-record.xml @@ -1,3 +1,21 @@ + +
Dates in the Usage Record Usage records include a start date and an end date. These dates define the period of time for which the raw usage number was calculated. If daily aggregation is used, the start date is midnight on the day in question and the end date is 23:59:59 on the day in question (with one exception; see below). A virtual machine could have been deployed at noon on that day, stopped at 6pm on that day, then started up again at 11pm. When usage is calculated on that day, there will be 7 hours of running VM usage (usage type 1) and 12 hours of allocated VM usage (usage type 2). If the same virtual machine runs for the entire next day, there will 24 hours of both running VM usage (type 1) and allocated VM usage (type 2). http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/c35153ce/docs/en-US/dedicated-ha-hosts.xml ---------------------------------------------------------------------- diff --git a/docs/en-US/dedicated-ha-hosts.xml b/docs/en-US/dedicated-ha-hosts.xml index e985142..ab50700 100644 --- a/docs/en-US/dedicated-ha-hosts.xml +++ b/docs/en-US/dedicated-ha-hosts.xml @@ -1,15 +1,34 @@ - %BOOK_ENTITIES; ]> + + +
Dedicated HA Hosts (v3.0.3 and greater) One or more hosts can be designated for use only by HA-enabled VMs that are restarting due to a host failure. Setting up a pool of such dedicated HA hosts as the recovery destination for all HA-enabled VMs is useful to: - Make it easier to determine which VMs have been restarted as part of the CloudPlatform high-availability function. If a VM is running on a dedicated HA host, then it must be an HA-enabled VM whose original host failed. (With one exception: It is possible for an administrator to manually migrate any VM to a dedicated HA host.). + Make it easier to determine which VMs have been restarted as part of the &PRODUCT; high-availability function. If a VM is running on a dedicated HA host, then it must be an HA-enabled VM whose original host failed. (With one exception: It is possible for an administrator to manually migrate any VM to a dedicated HA host.). Keep HA-enabled VMs from restarting on hosts which may be reserved for other purposes. The dedicated HA option is set through a special host tag when the host is created. To allow the administrator to dedicate hosts to only HA-enabled VMs, set the global configuration variable ha.tag to the desired tag (for example, "ha_host"), and restart the Management Server. Enter the value in the Host Tags field when adding the host(s) that you want to dedicate to HA-enabled VMs. If you set ha.tag, be sure to actually use that tag on at least one host in your cloud. If the tag specified in ha.tag is not set for any host in the cloud, the HA-enabled VMs will fail to restart after a crash. -
\ No newline at end of file +
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/c35153ce/docs/en-US/default-account-resource-limit.xml ---------------------------------------------------------------------- diff --git a/docs/en-US/default-account-resource-limit.xml b/docs/en-US/default-account-resource-limit.xml index 0ace634..abc313f 100644 --- a/docs/en-US/default-account-resource-limit.xml +++ b/docs/en-US/default-account-resource-limit.xml @@ -1,14 +1,33 @@ - %BOOK_ENTITIES; ]> + + +
Default Account Resource Limits You can limit resource use by accounts. The default limits are set using global configuration parameters, and they affect all accounts within a cloud. The relevant parameters are those beginning with max.account (max.account.snapshots, etc.).. To override a default limit for a particular account, set a per-account resource limit. - Log in to the CloudPlatform UI. + Log in to the &PRODUCT; UI. In the left navigation tree, click Accounts. Select the account you want to modify. The current limits are displayed. A value of -1 shows that there is no limit in place Click the Edit button @@ -18,5 +37,4 @@ editbutton.png: edits the settings. -
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/c35153ce/docs/en-US/default-template.xml ---------------------------------------------------------------------- diff --git a/docs/en-US/default-template.xml b/docs/en-US/default-template.xml index 4f4e583..c4741c9 100644 --- a/docs/en-US/default-template.xml +++ b/docs/en-US/default-template.xml @@ -1,11 +1,30 @@ - %BOOK_ENTITIES; ]> + + +
The Default Template - CloudPlatform includes a CentOS template. This template is downloaded by the Secondary Storage VM after the primary and secondary storage are configured. You can use this template in your production deployment or you can delete it and use custom templates. + &PRODUCT; includes a CentOS template. This template is downloaded by the Secondary Storage VM after the primary and secondary storage are configured. You can use this template in your production deployment or you can delete it and use custom templates. The root password for the default template is "password". A default template is provided for each of XenServer, KVM, and vSphere. The templates that are downloaded depend on the hypervisor type that is available in your cloud. Each template is approximately 2.5 GB physical size. The default template includes the standard iptables rules, which will block most access to the template excluding ssh. http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/c35153ce/docs/en-US/delete-templates.xml ---------------------------------------------------------------------- diff --git a/docs/en-US/delete-templates.xml b/docs/en-US/delete-templates.xml index d3f99b9..48d8fd1 100644 --- a/docs/en-US/delete-templates.xml +++ b/docs/en-US/delete-templates.xml @@ -1,8 +1,27 @@ - %BOOK_ENTITIES; ]> + + +
Deleting Templates Templates may be deleted. In general, when a template spans multiple Zones, only the copy that is selected for deletion will be deleted; the same template in other Zones will not be deleted. The provided CentOS template is an exception to this. If the provided CentOS template is deleted, it will be deleted from all Zones. http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/c35153ce/docs/en-US/deleting-vms.xml ---------------------------------------------------------------------- diff --git a/docs/en-US/deleting-vms.xml b/docs/en-US/deleting-vms.xml index a6cc0db..ab65fef 100644 --- a/docs/en-US/deleting-vms.xml +++ b/docs/en-US/deleting-vms.xml @@ -1,14 +1,33 @@ - %BOOK_ENTITIES; ]> + + +
Deleting VMs Users can delete their own virtual machines. A running virtual machine will be abruptly stopped before it is deleted. Administrators can delete any virtual machines. To delete a virtual machine: - 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 Instances. Choose the VM that you want to delete. Click the Destroy Instance button @@ -20,4 +39,3 @@
- http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/c35153ce/docs/en-US/deployment-architecture-overview.xml ---------------------------------------------------------------------- diff --git a/docs/en-US/deployment-architecture-overview.xml b/docs/en-US/deployment-architecture-overview.xml index 25f0825..2d46379 100644 --- a/docs/en-US/deployment-architecture-overview.xml +++ b/docs/en-US/deployment-architecture-overview.xml @@ -1,8 +1,27 @@ - %BOOK_ENTITIES; ]> + + +
Deployment Architecture Overview @@ -22,4 +41,4 @@ -
\ No newline at end of file +
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/c35153ce/docs/en-US/deployment_architecture_overview.xml ---------------------------------------------------------------------- diff --git a/docs/en-US/deployment_architecture_overview.xml b/docs/en-US/deployment_architecture_overview.xml index 08c1082..34d91d7 100644 --- a/docs/en-US/deployment_architecture_overview.xml +++ b/docs/en-US/deployment_architecture_overview.xml @@ -1,17 +1,35 @@ + +
Deployment Architecture Overview - A CloudStack installation consists of two parts: the Management Server and the cloud infrastructure that it manages. When you set up and manage a CloudStack cloud, you provision resources such as hosts, storage devices, and IP addresses into the Management Server, and the Management Server manages those resources. + A &PRODUCT; installation consists of two parts: the Management Server and the cloud infrastructure that it manages. When you set up and manage a &PRODUCT; cloud, you provision resources such as hosts, storage devices, and IP addresses into the Management Server, and the Management Server manages those resources. - The minimum installation consists of one machine running the CloudStack Management Server and another machine to act as the cloud infrastructure (in this case, a very simple infrastructure consisting of one host running hypervisor software). + The minimum installation consists of one machine running the &PRODUCT; Management Server and another machine to act as the cloud infrastructure (in this case, a very simple infrastructure consisting of one host running hypervisor software). - basic_deployment.png: Basic two-machine CloudStack deployment + basic_deployment.png: Basic two-machine &PRODUCT; deployment A more full-featured installation consists of a highly-available multi-node Management Server installation and up to thousands of hosts using any of several advanced networking setups. For information about deployment options, see Choosing a Deployment Architecture. http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/c35153ce/docs/en-US/detach-move-volumes.xml ---------------------------------------------------------------------- diff --git a/docs/en-US/detach-move-volumes.xml b/docs/en-US/detach-move-volumes.xml index 26c241c..6f241d5 100644 --- a/docs/en-US/detach-move-volumes.xml +++ b/docs/en-US/detach-move-volumes.xml @@ -1,16 +1,35 @@ - %BOOK_ENTITIES; ]> + + +
Attaching a Volume This procedure is different from moving disk volumes from one storage pool to another. See VM Storage Migration - A volume can be detached from a guest VM and attached to another guest. Both CloudPlatform administrators and users can detach volumes from VMs and move them to other VMs. + A volume can be detached from a guest VM and attached to another guest. Both &PRODUCT; administrators and users can detach volumes from VMs and move them to other VMs. If the two VMs are in different clusters, and the volume is large, it may take several minutes for the volume to be moved to the new VM. If the destination VM is running in the OVM hypervisor, the VM must be stopped before a new volume can be attached to it. - 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 bar, click Storage, and choose Volumes in Select View. Alternatively, if you know which VM the volume is attached to, you can click Instances, click the VM name, and click View Volumes. Click the name of the volume you want to detach, then click the Detach Disk button @@ -22,4 +41,3 @@ To move the volume to another VM, follow the steps in Attaching a Volume .
- http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/c35153ce/docs/en-US/developer-getting-started.xml ---------------------------------------------------------------------- diff --git a/docs/en-US/developer-getting-started.xml b/docs/en-US/developer-getting-started.xml index adfac34..82ef120 100644 --- a/docs/en-US/developer-getting-started.xml +++ b/docs/en-US/developer-getting-started.xml @@ -1,9 +1,27 @@ + +
Getting Started - To get started using the CloudStack API, you should have the following: + To get started using the &PRODUCT; API, you should have the following: - URL of the CloudStack server you wish to integrate with. + URL of the &PRODUCT; server you wish to integrate with. Both the API Key and Secret Key for an account. This should have been generated by the administrator of the cloud instance and given to you. Familiarity with HTTP GET/POST and query strings. Knowledge of either XML or JSON. http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/c35153ce/docs/en-US/developer-guide.xml ---------------------------------------------------------------------- diff --git a/docs/en-US/developer-guide.xml b/docs/en-US/developer-guide.xml index 77af46e..373ab29 100644 --- a/docs/en-US/developer-guide.xml +++ b/docs/en-US/developer-guide.xml @@ -1,8 +1,27 @@ - %BOOK_ENTITIES; ]> + + + Using the API http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/c35153ce/docs/en-US/developer-introduction.xml ---------------------------------------------------------------------- diff --git a/docs/en-US/developer-introduction.xml b/docs/en-US/developer-introduction.xml index d895253..f2ab1d4 100644 --- a/docs/en-US/developer-introduction.xml +++ b/docs/en-US/developer-introduction.xml @@ -1,8 +1,27 @@ - %BOOK_ENTITIES; ]> + + +
Introduction for Developers http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/c35153ce/docs/en-US/developer_guide.xml ---------------------------------------------------------------------- diff --git a/docs/en-US/developer_guide.xml b/docs/en-US/developer_guide.xml index eb174be..9606bab 100644 --- a/docs/en-US/developer_guide.xml +++ b/docs/en-US/developer_guide.xml @@ -1,8 +1,27 @@ - %BOOK_ENTITIES; ]> + + + Developer Guide http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/c35153ce/docs/en-US/disable-enable-zones-pods-clusters.xml ---------------------------------------------------------------------- diff --git a/docs/en-US/disable-enable-zones-pods-clusters.xml b/docs/en-US/disable-enable-zones-pods-clusters.xml index 94bf89e..7d52ae7 100644 --- a/docs/en-US/disable-enable-zones-pods-clusters.xml +++ b/docs/en-US/disable-enable-zones-pods-clusters.xml @@ -1,14 +1,33 @@ - %BOOK_ENTITIES; ]> + + +
Disabling and Enabling Zones, Pods, and Clusters You can enable or disable a zone, pod, or cluster without permanently removing it from the cloud. This is useful for maintenance or when there are problems that make a portion of the cloud infrastructure unreliable. No new allocations will be made to a disabled zone, pod, or cluster until its state is returned to Enabled. When a zone, pod, or cluster is first added to the cloud, it is Disabled by default. To disable and enable a zone, pod, or cluster: - Log in to the CloudPlatform UI as administrator + Log in to the &PRODUCT; UI as administrator In the left navigation bar, click Infrastructure. In Zones, click View More. http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/c35153ce/docs/en-US/disk-volume-usage-record-format.xml ---------------------------------------------------------------------- diff --git a/docs/en-US/disk-volume-usage-record-format.xml b/docs/en-US/disk-volume-usage-record-format.xml index c4b898e..7283698 100644 --- a/docs/en-US/disk-volume-usage-record-format.xml +++ b/docs/en-US/disk-volume-usage-record-format.xml @@ -1,3 +1,21 @@ + +
Disk Volume Usage Record Format For disk volumes, the following fields exist in a usage record. @@ -18,4 +36,3 @@ startdate, enddate – The range of time for which the usage is aggregated; see Dates in the Usage Record
- http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/c35153ce/docs/en-US/dns-dhcp.xml ---------------------------------------------------------------------- diff --git a/docs/en-US/dns-dhcp.xml b/docs/en-US/dns-dhcp.xml index dfebbd6..4d5bf00 100644 --- a/docs/en-US/dns-dhcp.xml +++ b/docs/en-US/dns-dhcp.xml @@ -1,8 +1,27 @@ - %BOOK_ENTITIES; ]> + + +
DNS and DHCP The Virtual Router provides DNS and DHCP services to the guests. It proxies DNS requests to the DNS server configured on the Availability Zone. http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/c35153ce/docs/en-US/domains.xml ---------------------------------------------------------------------- diff --git a/docs/en-US/domains.xml b/docs/en-US/domains.xml index 669b3d3..9d19c7e 100644 --- a/docs/en-US/domains.xml +++ b/docs/en-US/domains.xml @@ -1,10 +1,28 @@ - %BOOK_ENTITIES; ]> + + +
Domains If the LDAP server requires SSL, you need to enable it in the ldapConfig command by setting the parameters ssl, truststore, and truststorepass. Before enabling SSL for ldapConfig, you need to get the certificate which the LDAP server is using and add it to a trusted keystore. You will need to know the path to the keystore and the password. -