Releasing an IP Address

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 BF4D5E10B for ; Tue, 15 Jan 2013 09:36:59 +0000 (UTC) Received: (qmail 6838 invoked by uid 500); 15 Jan 2013 09:36:57 -0000 Delivered-To: apmail-incubator-cloudstack-commits-archive@incubator.apache.org Received: (qmail 6485 invoked by uid 500); 15 Jan 2013 09:36:57 -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 98192 invoked by uid 99); 15 Jan 2013 09:36:32 -0000 Received: from tyr.zones.apache.org (HELO tyr.zones.apache.org) (140.211.11.114) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 15 Jan 2013 09:36:32 +0000 Received: by tyr.zones.apache.org (Postfix, from userid 65534) id 41C8D1DAC7; Tue, 15 Jan 2013 09:36:32 +0000 (UTC) Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 8bit From: widodh@apache.org To: cloudstack-commits@incubator.apache.org X-Mailer: ASF-Git Admin Mailer Subject: [11/52] [partial] Remove docs/tmp (partial revert) Message-Id: <20130115093632.41C8D1DAC7@tyr.zones.apache.org> Date: Tue, 15 Jan 2013 09:36:32 +0000 (UTC) http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/9b4ee042/docs/tmp/en-US/xml/release-ip-address.xml ---------------------------------------------------------------------- diff --git a/docs/tmp/en-US/xml/release-ip-address.xml b/docs/tmp/en-US/xml/release-ip-address.xml deleted file mode 100644 index 7f8fe6c..0000000 --- a/docs/tmp/en-US/xml/release-ip-address.xml +++ /dev/null @@ -1,70 +0,0 @@ - - -%BOOK_ENTITIES; -]> -

- Releasing an IP Address - - - - 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. - - - - - Click the IP address you want to release. - - - - - - Click the Release IP button - - - - - - ReleaseIPButton.png: button to release an IP - - - - . - - - - -

- - http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/9b4ee042/docs/tmp/en-US/xml/release-ip-for-vpc.xml ---------------------------------------------------------------------- diff --git a/docs/tmp/en-US/xml/release-ip-for-vpc.xml b/docs/tmp/en-US/xml/release-ip-for-vpc.xml deleted file mode 100644 index 5016062..0000000 --- a/docs/tmp/en-US/xml/release-ip-for-vpc.xml +++ /dev/null @@ -1,126 +0,0 @@ - - -%BOOK_ENTITIES; -]> -

- Releasing an IP Address Alloted to a VPC - - The IP address is a limited resource. If you no longer need a particular IP, you can disassociate it from its VPC and return it to the pool of available addresses. An IP address can be released from its tier, only when all the networking ( port forwarding, load balancing, or StaticNAT ) rules are removed for this IP address. The released IP address will still belongs to the same VPC. - - - - - Log in to the &PRODUCT; UI as an administrator or end user. - - - - - - In the left navigation, choose Network. - - - - - - In the Select view, select VPC. - - - All the VPCs that you have created for the account is listed in the page. - - - - - - Click the Configure button of the VPC whose IP you want to release. - - - The VPC page is displayed where all the tiers you created are listed in a diagram. - - - - - - Click the Settings icon. - - - The following options are displayed. - - - - - IP Addresses - - - - - - Gateways - - - - - - Site-to-Site VPN - - - - - - Network ACLs - - - - - - - - - - Select IP Addresses. - - - The IP Addresses page is displayed. - - - - - - Click the IP you want to release. - - - - - - In the Details tab, click the Release IP button - - - - - - release-ip-icon.png: button to release an IP. - - - - - - - - -

- - http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/9b4ee042/docs/tmp/en-US/xml/remove-member-from-project.xml ---------------------------------------------------------------------- diff --git a/docs/tmp/en-US/xml/remove-member-from-project.xml b/docs/tmp/en-US/xml/remove-member-from-project.xml deleted file mode 100644 index ed11864..0000000 --- a/docs/tmp/en-US/xml/remove-member-from-project.xml +++ /dev/null @@ -1,80 +0,0 @@ - - -%BOOK_ENTITIES; -]> -

- Removing a Member From a Project - - When a member is removed from a project, the member’s resources continue to be owned by the project. The former project member cannot create any new resources within the project or use any of the project’s existing resources. - - - A member of a project can be removed by the project administrator, the domain administrator of the domain the project belongs to or of its parent domain, or the &PRODUCT; root administrator. - - - - - Log in to the &PRODUCT; UI. - - - - - In the left navigation, click Projects. - - - - - In Select View, choose Projects. - - - - - Click the name of the project. - - - - - Click the Accounts tab. - - - - - Click the name of the member. - - - - - Click the Delete button. - - - - - - deletebutton.png: Removes a member - - - - - - - - -

- - http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/9b4ee042/docs/tmp/en-US/xml/remove-tier.xml ---------------------------------------------------------------------- diff --git a/docs/tmp/en-US/xml/remove-tier.xml b/docs/tmp/en-US/xml/remove-tier.xml deleted file mode 100644 index 6c108e7..0000000 --- a/docs/tmp/en-US/xml/remove-tier.xml +++ /dev/null @@ -1,78 +0,0 @@ - - -%BOOK_ENTITIES; -]> -

- Removing Tiers - - You can remove a tier from a VPC. A removed tier cannot be revoked. When a tier is removed, only the resources of the tier are expunged. All the network rules (port forwarding, load balancing and staticNAT) and the IP addresses associated to the tier are removed. The IP address still be belonging to the same VPC. - - - - - Log in to the &PRODUCT; UI as an administrator or end user. - - - - - - In the left navigation, choose Network. - - - - - - In the Select view, select VPC. - - - All the VPC that you have created for the account is listed in the page. - - - - - - Click the Configure button of the VPC for which you want to set up tiers. - - - The Configure VPC page is displayed. Locate the tier you want to work with. - - - - - - Click the Remove VPC button: - - - - - - - remove-tier.png: removing a tier from a vpc. - - - - - Wait for some time for the tier to be removed. - - - - - -

- - http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/9b4ee042/docs/tmp/en-US/xml/remove-vpc.xml ---------------------------------------------------------------------- diff --git a/docs/tmp/en-US/xml/remove-vpc.xml b/docs/tmp/en-US/xml/remove-vpc.xml deleted file mode 100644 index 021480d..0000000 --- a/docs/tmp/en-US/xml/remove-vpc.xml +++ /dev/null @@ -1,99 +0,0 @@ - - -%BOOK_ENTITIES; -]> -

- Editing, Restarting, and Removing a Virtual Private Cloud - - - Ensure that all the tiers are removed before you remove a VPC. - - - - - - - Log in to the &PRODUCT; UI as an administrator or end user. - - - - - - In the left navigation, choose Network. - - - - - - In the Select view, select VPC. - - - All the VPCs that you have created for the account is listed in the page. - - - - - - Select the VPC you want to work with. - - - - - - To remove, click the Remove VPC button - - - - - - remove-vpc.png: button to remove a VPC - - - - - - You can edit the name and description of a VPC. To do that, select the VPC, then click the Edit button. - - - - - - edit-icon.png: button to edit a VPC - - - - - - To restart a VPC, select the VPC, then click the Restart button. - - - - - - restart-vpc.png: button to restart a VPC - - - - - - - - -

- - http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/9b4ee042/docs/tmp/en-US/xml/removed-API-commands.xml ---------------------------------------------------------------------- diff --git a/docs/tmp/en-US/xml/removed-API-commands.xml b/docs/tmp/en-US/xml/removed-API-commands.xml deleted file mode 100644 index 6c9cb0e..0000000 --- a/docs/tmp/en-US/xml/removed-API-commands.xml +++ /dev/null @@ -1,40 +0,0 @@ - - -%BOOK_ENTITIES; -]> -

- Removed API commands - - - - createConfiguration (Adds configuration value) - - - - - configureSimulator (Configures simulator) - - - - - -

- - http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/9b4ee042/docs/tmp/en-US/xml/removing-hosts.xml ---------------------------------------------------------------------- diff --git a/docs/tmp/en-US/xml/removing-hosts.xml b/docs/tmp/en-US/xml/removing-hosts.xml deleted file mode 100644 index c03f6179..0000000 --- a/docs/tmp/en-US/xml/removing-hosts.xml +++ /dev/null @@ -1,31 +0,0 @@ - - -%BOOK_ENTITIES; -]> -

- Removing Hosts - - Hosts can be removed from the cloud as needed. The procedure to remove a host depends on the hypervisor type. - - - -

- - http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/9b4ee042/docs/tmp/en-US/xml/removing-vsphere-hosts.xml ---------------------------------------------------------------------- diff --git a/docs/tmp/en-US/xml/removing-vsphere-hosts.xml b/docs/tmp/en-US/xml/removing-vsphere-hosts.xml deleted file mode 100644 index 252ef21..0000000 --- a/docs/tmp/en-US/xml/removing-vsphere-hosts.xml +++ /dev/null @@ -1,29 +0,0 @@ - - -%BOOK_ENTITIES; -]> -

- Removing vSphere Hosts - - To remove this type of host, first place it in maintenance mode, as described in . Then use &PRODUCT; to remove the host. &PRODUCT; will not direct commands to a host that has been removed using &PRODUCT;. However, the host may still exist in the vCenter cluster. - -

- - http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/9b4ee042/docs/tmp/en-US/xml/removing-xenserver-kvm-hosts.xml ---------------------------------------------------------------------- diff --git a/docs/tmp/en-US/xml/removing-xenserver-kvm-hosts.xml b/docs/tmp/en-US/xml/removing-xenserver-kvm-hosts.xml deleted file mode 100644 index 5c5ad0c..0000000 --- a/docs/tmp/en-US/xml/removing-xenserver-kvm-hosts.xml +++ /dev/null @@ -1,53 +0,0 @@ - - -%BOOK_ENTITIES; -]> -

- Removing XenServer and KVM Hosts - - A node cannot be removed from a cluster until it has been placed in maintenance mode. This will ensure that all of the VMs on it have been migrated to other Hosts. To remove a Host from the cloud: - - - - - Place the node in maintenance mode. - - - See . - - - - - For KVM, stop the cloud-agent service. - - - - - Use the UI option to remove the node. - - - Then you may power down the Host, re-use its IP address, re-install it, etc - - - - -

- - http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/9b4ee042/docs/tmp/en-US/xml/requirements-templates.xml ---------------------------------------------------------------------- diff --git a/docs/tmp/en-US/xml/requirements-templates.xml b/docs/tmp/en-US/xml/requirements-templates.xml deleted file mode 100644 index 78572e4..0000000 --- a/docs/tmp/en-US/xml/requirements-templates.xml +++ /dev/null @@ -1,38 +0,0 @@ - - -%BOOK_ENTITIES; -]> -

- Requirements for Templates - - - - For XenServer, install PV drivers / Xen tools on each template that you create. This will enable live migration and clean guest shutdown. - - - - - For vSphere, install VMware Tools on each template that you create. This will enable console view to work properly. - - - -

- - http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/9b4ee042/docs/tmp/en-US/xml/resizing-volumes.xml ---------------------------------------------------------------------- diff --git a/docs/tmp/en-US/xml/resizing-volumes.xml b/docs/tmp/en-US/xml/resizing-volumes.xml deleted file mode 100644 index 8a89eff..0000000 --- a/docs/tmp/en-US/xml/resizing-volumes.xml +++ /dev/null @@ -1,65 +0,0 @@ - - -%BOOK_ENTITIES; -]> -

- Resizing Volumes - - &PRODUCT; does not provide the ability to resize root disks or data disks; the disk size is fixed based on the template used to create the VM. However, the tool VHD Resizer), while not officially supported by Cloud.com or Citrix, might provide a workaround. To increase disk size with VHD Resizer: - - - - - Get the VHD from the secondary storage. - - - - - Import it into VHD Resizer. - - - - - Resize the VHD. - - - - - Upload the new VHD. - - - - - Create a new VM. - - - - - Take a snapshot, then create a new template from that snapshot. - - - For more information, see How to Resize a Provisioning Server 5 Virtual Disk at the Citrix Knowledge Center - - - - -

- - http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/9b4ee042/docs/tmp/en-US/xml/response-formats.xml ---------------------------------------------------------------------- diff --git a/docs/tmp/en-US/xml/response-formats.xml b/docs/tmp/en-US/xml/response-formats.xml deleted file mode 100644 index 803da8d..0000000 --- a/docs/tmp/en-US/xml/response-formats.xml +++ /dev/null @@ -1,63 +0,0 @@ - - -%BOOK_ENTITIES; -]> -

- Response Formats: XML and JSON - - CloudStack supports two formats as the response to an API call. The default response is XML. If you would like the response to be in JSON, add &response=json to the Command String. - - - Sample XML Response: - - - - <listipaddressesresponse> - <allocatedipaddress> - <ipaddress>192.168.10.141</ipaddress> - <allocated>2009-09-18T13:16:10-0700</allocated> - <zoneid>4</zoneid> - <zonename>WC</zonename> - <issourcenat>true</issourcenat> - </allocatedipaddress> - </listipaddressesresponse> - - - Sample JSON Response: - - - - { "listipaddressesresponse" : - { "allocatedipaddress" : - [ - { - "ipaddress" : "192.168.10.141", - "allocated" : "2009-09-18T13:16:10-0700", - "zoneid" : "4", - "zonename" : "WC", - "issourcenat" : "true" - } - ] - } - } - -

- - http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/9b4ee042/docs/tmp/en-US/xml/responses.xml ---------------------------------------------------------------------- diff --git a/docs/tmp/en-US/xml/responses.xml b/docs/tmp/en-US/xml/responses.xml deleted file mode 100644 index e7cdf13..0000000 --- a/docs/tmp/en-US/xml/responses.xml +++ /dev/null @@ -1,29 +0,0 @@ - - -%BOOK_ENTITIES; -]> -

- Responses - - - -

- - http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/9b4ee042/docs/tmp/en-US/xml/roles.xml ---------------------------------------------------------------------- diff --git a/docs/tmp/en-US/xml/roles.xml b/docs/tmp/en-US/xml/roles.xml deleted file mode 100644 index 66ad6f6..0000000 --- a/docs/tmp/en-US/xml/roles.xml +++ /dev/null @@ -1,47 +0,0 @@ - - -%BOOK_ENTITIES; -]> -

- Roles - - The &PRODUCT; API supports three access roles: - - - - - Root Admin. Access to all features of the cloud, including both virtual and physical resource management. - - - - - Domain Admin. Access to only the virtual resources of the clouds that belong to the administrator’s domain. - - - - - User. Access to only the features that allow management of the user’s virtual instances, storage, and network. - - - - -

- - http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/9b4ee042/docs/tmp/en-US/xml/root-admin-ui-overview.xml ---------------------------------------------------------------------- diff --git a/docs/tmp/en-US/xml/root-admin-ui-overview.xml b/docs/tmp/en-US/xml/root-admin-ui-overview.xml deleted file mode 100644 index d974b32..0000000 --- a/docs/tmp/en-US/xml/root-admin-ui-overview.xml +++ /dev/null @@ -1,29 +0,0 @@ - - -%BOOK_ENTITIES; -]> -

- Root Administrator's UI Overview - - The &PRODUCT; UI helps the &PRODUCT; administrator provision, view, and manage the cloud infrastructure, domains, user accounts, projects, and configuration settings. The first time you start the UI after a fresh Management Server installation, you can choose to follow a guided tour to provision your cloud infrastructure. On subsequent logins, the dashboard of the logged-in user appears. The various links in this screen and the navigation bar on the left provide access to a variety of administrative functions. The root administrator can also use the UI to perform all the same tasks that are present in the end-user’s UI. - -

- - http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/9b4ee042/docs/tmp/en-US/xml/runtime-allocation-virtual-network-resources.xml ---------------------------------------------------------------------- diff --git a/docs/tmp/en-US/xml/runtime-allocation-virtual-network-resources.xml b/docs/tmp/en-US/xml/runtime-allocation-virtual-network-resources.xml deleted file mode 100644 index 35fd23b..0000000 --- a/docs/tmp/en-US/xml/runtime-allocation-virtual-network-resources.xml +++ /dev/null @@ -1,29 +0,0 @@ - - -%BOOK_ENTITIES; -]> -

- Runtime Allocation of Virtual Network Resources - - When you define a new virtual network, all your settings for that network are stored in &PRODUCT;. The actual network resources are activated only when the first virtual machine starts in the network. When all virtual machines have left the virtual network, the network resources are garbage collected so they can be allocated again. This helps to conserve network resources.. - -

- - http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/9b4ee042/docs/tmp/en-US/xml/runtime-behavior-of-primary-storage.xml ---------------------------------------------------------------------- diff --git a/docs/tmp/en-US/xml/runtime-behavior-of-primary-storage.xml b/docs/tmp/en-US/xml/runtime-behavior-of-primary-storage.xml deleted file mode 100644 index 3122b38..0000000 --- a/docs/tmp/en-US/xml/runtime-behavior-of-primary-storage.xml +++ /dev/null @@ -1,35 +0,0 @@ - - -%BOOK_ENTITIES; -]> -

- Runtime Behavior of Primary Storage - - Root volumes are created automatically when a virtual machine is created. Root volumes are deleted when the VM is destroyed. Data volumes can be created and dynamically attached to VMs. Data volumes are not deleted when VMs are destroyed. - - - Administrators should monitor the capacity of primary storage devices and add additional primary storage as needed. See the Advanced Installation Guide. - - - Administrators add primary storage to the system by creating a &PRODUCT; storage pool. Each storage pool is associated with a cluster. - -

- - http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/9b4ee042/docs/tmp/en-US/xml/runtime-internal-comm-req.xml ---------------------------------------------------------------------- diff --git a/docs/tmp/en-US/xml/runtime-internal-comm-req.xml b/docs/tmp/en-US/xml/runtime-internal-comm-req.xml deleted file mode 100644 index d37a6c1..0000000 --- a/docs/tmp/en-US/xml/runtime-internal-comm-req.xml +++ /dev/null @@ -1,45 +0,0 @@ - - -%BOOK_ENTITIES; -]> -

- Runtime Internal Communications Requirements - - - - The Management Servers communicate with each other to coordinate tasks. This communication uses TCP on ports 8250 and 9090. - - - - - - The console proxy VMs connect to all hosts in the zone over the management traffic network. Therefore the management traffic network of any given pod in the zone must have connectivity to the management traffic network of all other pods in the zone. - - - - - - The secondary storage VMs and console proxy VMs connect to the Management Server on port 8250. If you are using multiple Management Servers, the load balanced IP address of the Management Servers on port 8250 must be reachable. - - - - - -

- - http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/9b4ee042/docs/tmp/en-US/xml/scheduled-maintenance-maintenance-mode-hosts.xml ---------------------------------------------------------------------- diff --git a/docs/tmp/en-US/xml/scheduled-maintenance-maintenance-mode-hosts.xml b/docs/tmp/en-US/xml/scheduled-maintenance-maintenance-mode-hosts.xml deleted file mode 100644 index ef639a7..0000000 --- a/docs/tmp/en-US/xml/scheduled-maintenance-maintenance-mode-hosts.xml +++ /dev/null @@ -1,29 +0,0 @@ - - -%BOOK_ENTITIES; -]> -

- Scheduled Maintenance and Maintenance Mode for Hosts - - You can place a host into maintenance mode. When maintenance mode is activated, the host becomes unavailable to receive new guest VMs, and the guest VMs already running on the host are seamlessly migrated to another host not in maintenance mode. This migration uses live migration technology and does not interrupt the execution of the guest. - -

- - http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/9b4ee042/docs/tmp/en-US/xml/search-base.xml ---------------------------------------------------------------------- diff --git a/docs/tmp/en-US/xml/search-base.xml b/docs/tmp/en-US/xml/search-base.xml deleted file mode 100644 index f86fbc9..0000000 --- a/docs/tmp/en-US/xml/search-base.xml +++ /dev/null @@ -1,81 +0,0 @@ - - -%BOOK_ENTITIES; -]> -

- Search Base - - An LDAP query is relative to a given node of the LDAP directory tree, called the search base. The search base is the distinguished name (DN) of a level of the directory tree below which all users can be found. The users can be in the immediate base directory or in some subdirectory. The search base may be equivalent to the organization, group, or domain name. The syntax for writing a DN varies depending on which LDAP server you are using. A full discussion of distinguished names is outside the scope of our documentation. The following table shows some examples of search bases to find users in the testing department.. - - - - - - - - LDAP Server - - - - - Example Search Base DN - - - - - - - - - - - ApacheDS - - - - - ou=testing,o=project - - - - - - - - Active Directory - - - - - OU=testing, DC=company - - - - - - - - - - - -

- - http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/9b4ee042/docs/tmp/en-US/xml/search-user-bind-dn.xml ---------------------------------------------------------------------- diff --git a/docs/tmp/en-US/xml/search-user-bind-dn.xml b/docs/tmp/en-US/xml/search-user-bind-dn.xml deleted file mode 100644 index 4faf760..0000000 --- a/docs/tmp/en-US/xml/search-user-bind-dn.xml +++ /dev/null @@ -1,79 +0,0 @@ - - -%BOOK_ENTITIES; -]> -

- Search User Bind DN - - The bind DN is the user on the external LDAP server permitted to search the LDAP directory within the defined search base. When the DN is returned, the DN and passed password are used to authenticate the &PRODUCT; user with an LDAP bind. A full discussion of bind DNs is outside the scope of our documentation. The following table shows some examples of bind DNs. - - - - - - - - LDAP Server - - - - - Example Bind DN - - - - - - - - - - - ApacheDS - - - - - cn=Administrator,dc=testing,ou=project,ou=org - - - - - - - - Active Directory - - - - - CN=Administrator, OU=testing, DC=company, DC=com - - - - - - - - - -

- - http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/9b4ee042/docs/tmp/en-US/xml/secondary-storage-add.xml ---------------------------------------------------------------------- diff --git a/docs/tmp/en-US/xml/secondary-storage-add.xml b/docs/tmp/en-US/xml/secondary-storage-add.xml deleted file mode 100644 index cf0f89d..0000000 --- a/docs/tmp/en-US/xml/secondary-storage-add.xml +++ /dev/null @@ -1,95 +0,0 @@ - - -%BOOK_ENTITIES; -]> -

- Add Secondary Storage -

- System Requirements for Secondary Storage - - - - NFS storage appliance or Linux NFS server - - - - - (Optional) OpenStack Object Storage (Swift) (see http://swift.openstack.org) - - - - - 100GB minimum capacity - - - - - A secondary storage device must be located in the same zone as the guest VMs it serves. - - - - - Each Secondary Storage server must be available to all hosts in the zone. - - - - - -

- -

- Adding Secondary Storage - - When you create a new zone, the first secondary storage is added as part of that procedure. You can add secondary storage servers at any time to add more servers to an existing zone. - - - - Be sure there is nothing stored on the server. Adding the server to &PRODUCT; will destroy any existing data. - - - - - - If you are going to use Swift for cloud-wide secondary storage, you must add the Swift storage to &PRODUCT; before you add the local zone secondary storage servers. See . - - - - - To prepare for local zone secondary storage, you should have created and mounted an NFS share during Management Server installation. See . - - - - - Make sure you prepared the system VM template during Management Server installation. See . - - - - - Now that the secondary storage server for per-zone storage is prepared, add it to &PRODUCT;. Secondary storage is added as part of the procedure for adding a new zone. See . - - - - - -

- -

- - http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/9b4ee042/docs/tmp/en-US/xml/secondary-storage-outage-and-data-loss.xml ---------------------------------------------------------------------- diff --git a/docs/tmp/en-US/xml/secondary-storage-outage-and-data-loss.xml b/docs/tmp/en-US/xml/secondary-storage-outage-and-data-loss.xml deleted file mode 100644 index 0261421..0000000 --- a/docs/tmp/en-US/xml/secondary-storage-outage-and-data-loss.xml +++ /dev/null @@ -1,32 +0,0 @@ - - -%BOOK_ENTITIES; -]> -

- Secondary Storage Outage and Data Loss - - For a Zone that has only one secondary storage server, a secondary storage outage will have feature level impact to the system but will not impact running guest VMs. It may become impossible to create a VM with the selected template for a user. A user may also not be able to save snapshots or examine/restore saved snapshots. These features will automatically be available when the secondary storage comes back online. - - - Secondary storage data loss will impact recently added user data including templates, snapshots, and ISO images. Secondary storage should be backed up periodically. Multiple secondary storage servers can be provisioned within each zone to increase the scalability of the system. - -

- - http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/9b4ee042/docs/tmp/en-US/xml/secondary-storage-vm.xml ---------------------------------------------------------------------- diff --git a/docs/tmp/en-US/xml/secondary-storage-vm.xml b/docs/tmp/en-US/xml/secondary-storage-vm.xml deleted file mode 100644 index 73e6bfd..0000000 --- a/docs/tmp/en-US/xml/secondary-storage-vm.xml +++ /dev/null @@ -1,38 +0,0 @@ - - -%BOOK_ENTITIES; -]> -

- Secondary Storage VM - - In addition to the hosts, &PRODUCT;’s Secondary Storage VM mounts and writes to secondary storage. - - - Submissions to secondary storage go through the Secondary Storage VM. The Secondary Storage VM can retrieve templates and ISO images from URLs using a variety of protocols. - - - The secondary storage VM provides a background task that takes care of a variety of secondary storage activities: downloading a new template to a Zone, copying templates between Zones, and snapshot backups. - - - The administrator can log in to the secondary storage VM if needed. - -

- - http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/9b4ee042/docs/tmp/en-US/xml/secondary-storage.xml ---------------------------------------------------------------------- diff --git a/docs/tmp/en-US/xml/secondary-storage.xml b/docs/tmp/en-US/xml/secondary-storage.xml deleted file mode 100644 index 182b91b..0000000 --- a/docs/tmp/en-US/xml/secondary-storage.xml +++ /dev/null @@ -1,32 +0,0 @@ - - -%BOOK_ENTITIES; -]> -

- Secondary Storage - - This section gives concepts and technical details about &PRODUCT; secondary storage. For information about how to install and configure secondary storage through the &PRODUCT; UI, see the Advanced Installation Guide. - - - - -

- - http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/9b4ee042/docs/tmp/en-US/xml/security-groups.xml ---------------------------------------------------------------------- diff --git a/docs/tmp/en-US/xml/security-groups.xml b/docs/tmp/en-US/xml/security-groups.xml deleted file mode 100644 index 4b2b604..0000000 --- a/docs/tmp/en-US/xml/security-groups.xml +++ /dev/null @@ -1,30 +0,0 @@ - - -%BOOK_ENTITIES; -]> -

- Security Groups - - - - -

- - http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/9b4ee042/docs/tmp/en-US/xml/security-req.xml ---------------------------------------------------------------------- diff --git a/docs/tmp/en-US/xml/security-req.xml b/docs/tmp/en-US/xml/security-req.xml deleted file mode 100644 index e4a727b..0000000 --- a/docs/tmp/en-US/xml/security-req.xml +++ /dev/null @@ -1,27 +0,0 @@ - - -%BOOK_ENTITIES; -]> -

- Security Requirements - - The public Internet must not be able to access port 8096 or port 8250 on the Management Server. - -

- - http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/9b4ee042/docs/tmp/en-US/xml/send-projects-membership-invitation.xml ---------------------------------------------------------------------- diff --git a/docs/tmp/en-US/xml/send-projects-membership-invitation.xml b/docs/tmp/en-US/xml/send-projects-membership-invitation.xml deleted file mode 100644 index 675a51a..0000000 --- a/docs/tmp/en-US/xml/send-projects-membership-invitation.xml +++ /dev/null @@ -1,85 +0,0 @@ - - -%BOOK_ENTITIES; -]> -

- Sending Project Membership Invitations - - Use these steps to add a new member to a project if the invitations feature is enabled in the cloud as described in . If the invitations feature is not turned on, use the procedure in Adding Project Members From the 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. - - - - - Click the Invitations tab. - - - - - In Add by, select one of the following: - - - - - Account – The invitation will appear in the user’s Invitations tab in the Project View. See Using the Project View. - - - - - Email – The invitation will be sent to the user’s email address. Each emailed invitation includes a unique code called a token which the recipient will provide back to &PRODUCT; when accepting the invitation. Email invitations will work only if the global parameters related to the SMTP server have been set. See . - - - - - - - - Type the user name or email address of the new member you want to add, and click Invite. Type the &PRODUCT; user name if you chose Account in the previous step. If you chose Email, type the email address. You can invite only people who have an account in this cloud within the same domain as the project. However, you can send the invitation to any email address. - - - - - To view and manage the invitations you have sent, return to this tab. When an invitation is accepted, the new member will appear in the project’s Accounts tab. - - - - -

- - http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/9b4ee042/docs/tmp/en-US/xml/separate_storage_network.xml ---------------------------------------------------------------------- diff --git a/docs/tmp/en-US/xml/separate_storage_network.xml b/docs/tmp/en-US/xml/separate_storage_network.xml deleted file mode 100644 index 3b5103a..0000000 --- a/docs/tmp/en-US/xml/separate_storage_network.xml +++ /dev/null @@ -1,27 +0,0 @@ - - -%BOOK_ENTITIES; -]> -

- Separate Storage Network - - In the large-scale redundant setup described in the previous section, storage traffic can overload the management network. A separate storage network is optional for deployments. Storage protocols such as iSCSI are sensitive to network delays. A separate storage network ensures guest network traffic contention does not impact storage performance. - -

- - http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/9b4ee042/docs/tmp/en-US/xml/service-offerings.xml ---------------------------------------------------------------------- diff --git a/docs/tmp/en-US/xml/service-offerings.xml b/docs/tmp/en-US/xml/service-offerings.xml deleted file mode 100644 index 2ba538b..0000000 --- a/docs/tmp/en-US/xml/service-offerings.xml +++ /dev/null @@ -1,38 +0,0 @@ - - -%BOOK_ENTITIES; -]> -

- Service Offerings - - vCenter Maintenance Mode - - - XenServer and Maintenance Mode - - - vCenter Maintenance Mode - - - XenServer and Maintenance Mode - -

- - http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/9b4ee042/docs/tmp/en-US/xml/set-database-buffer-pool-size.xml ---------------------------------------------------------------------- diff --git a/docs/tmp/en-US/xml/set-database-buffer-pool-size.xml b/docs/tmp/en-US/xml/set-database-buffer-pool-size.xml deleted file mode 100644 index 91a263d..0000000 --- a/docs/tmp/en-US/xml/set-database-buffer-pool-size.xml +++ /dev/null @@ -1,56 +0,0 @@ - - -%BOOK_ENTITIES; -]> -

- Set Database Buffer Pool Size - - It is important to provide enough memory space for the MySQL database to cache data and indexes: - - - - - Edit the Tomcat configuration file: - - -/etc/my.cnf - - - - Insert the following line in the [mysqld] section, below the datadir line. Use a value that is appropriate for your situation. We recommend setting the buffer pool at 40% of RAM if MySQL is on the same server as the management server or 70% of RAM if MySQL has a dedicated server. The following example assumes a dedicated server with 1024M of RAM. - - -innodb_buffer_pool_size=700M - - - - Restart the MySQL service. - - -# service mysqld restart - - - - - For more information about the buffer pool, see "The InnoDB Buffer Pool" at MySQL Reference Manual. - -

- - http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/9b4ee042/docs/tmp/en-US/xml/set-global-project-resource-limits.xml ---------------------------------------------------------------------- diff --git a/docs/tmp/en-US/xml/set-global-project-resource-limits.xml b/docs/tmp/en-US/xml/set-global-project-resource-limits.xml deleted file mode 100644 index fcec205..0000000 --- a/docs/tmp/en-US/xml/set-global-project-resource-limits.xml +++ /dev/null @@ -1,142 +0,0 @@ - - -%BOOK_ENTITIES; -]> -

- Setting the Global Project Resource Limits - - - - Log in as administrator to the &PRODUCT; UI. - - - - - - In the left navigation, click Global Settings. - - - - - - In the search box, type max.projects and click the search button. - - - - - - In the search results, you will see the parameters you can use to set per-project maximum resource amounts that apply to all projects in the cloud. No project can have more resources, but an individual project can have lower limits. Click the edit button to set each parameter. - - - - - - editbutton.png: Edits parameters - - - - - - - - - - - max.project.public.ips - - - - - Maximum number of public IP addresses that can be owned by any project in the cloud. See About Public IP Addresses. - - - - - - - - max.project.snapshots - - - - - Maximum number of snapshots that can be owned by any project in the cloud. See Working with Snapshots. - - - - - - - - max.project.templates - - - - - Maximum number of templates that can be owned by any project in the cloud. See Working with Templates. - - - - - - - - max.project.uservms - - - - - Maximum number of guest virtual machines that can be owned by any project in the cloud. See Working With Virtual Machines. - - - - - - - - max.project.volumes - - - - - Maximum number of data volumes that can be owned by any project in the cloud. See Working with Volumes. - - - - - - - - - - - - - - - Restart the Management Server. - - -# service cloud-management restart - - - - -

- - http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/9b4ee042/docs/tmp/en-US/xml/set-monitor-total-vm-limits-per-host.xml ---------------------------------------------------------------------- diff --git a/docs/tmp/en-US/xml/set-monitor-total-vm-limits-per-host.xml b/docs/tmp/en-US/xml/set-monitor-total-vm-limits-per-host.xml deleted file mode 100644 index 12f2323..0000000 --- a/docs/tmp/en-US/xml/set-monitor-total-vm-limits-per-host.xml +++ /dev/null @@ -1,29 +0,0 @@ - - -%BOOK_ENTITIES; -]> -

- Set and Monitor Total VM Limits per Host - - The &PRODUCT; 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 &PRODUCT; 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 VM s, use the &PRODUCT; UI to disable allocation of more VMs to the cluster. - -

- - http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/9b4ee042/docs/tmp/en-US/xml/set-per-project-resource-limits.xml ---------------------------------------------------------------------- diff --git a/docs/tmp/en-US/xml/set-per-project-resource-limits.xml b/docs/tmp/en-US/xml/set-per-project-resource-limits.xml deleted file mode 100644 index 1282f3a..0000000 --- a/docs/tmp/en-US/xml/set-per-project-resource-limits.xml +++ /dev/null @@ -1,75 +0,0 @@ - - -%BOOK_ENTITIES; -]> -

- Setting Per-Project Resource Limits - - The &PRODUCT; root administrator or the domain administrator of the domain where the project resides can set new resource limits for an individual project. The project owner can set resource limits only if the owner is also a domain or root administrator. - - - The new limits must be below the global default limits set by the &PRODUCT; administrator (as described in ). If the project already owns more of a given type of resource than the new maximum, the resources are not affected; however, the project can not add any new resources of that type until the total drops below the new limit. - - - - - Log in as administrator 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. - - - - - - Click the Resources tab. This tab lists the current maximum amount that the project is allowed to own for each type of resource. - - - - - - Type new values for one or more resources. - - - - - - Click Apply. - - - - - -

- - http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/9b4ee042/docs/tmp/en-US/xml/set-projects-creator-permissions.xml ---------------------------------------------------------------------- diff --git a/docs/tmp/en-US/xml/set-projects-creator-permissions.xml b/docs/tmp/en-US/xml/set-projects-creator-permissions.xml deleted file mode 100644 index 1832558..0000000 --- a/docs/tmp/en-US/xml/set-projects-creator-permissions.xml +++ /dev/null @@ -1,93 +0,0 @@ - - -%BOOK_ENTITIES; -]> -

- Setting Project Creator Permissions - - You can configure &PRODUCT; to allow any user to create a new project, or you can restrict that ability to just &PRODUCT; administrators. - - - - - Log in as administrator to the &PRODUCT; UI. - - - - - - In the left navigation, click Global Settings. - - - - - - In the search box, type allow.user.create.projects. - - - - - - Click the edit button to set the parameter. - - - - - - editbutton.png: Edits parameters - - - - - - - - - - - allow.user.create.projects - - - - - Set to true to allow end users to create projects. Set to false if you want only the &PRODUCT; root administrator and domain administrators to create projects. - - - - - - - - - - - - - - - Restart the Management Server. - - -# service cloud-management restart - - - - -

- -