Management Server Installation Overview

In-Reply-To: <70dce7e46df64989b9cdbc3fddef9604@git.apache.org> References: <70dce7e46df64989b9cdbc3fddef9604@git.apache.org> X-Mailer: ASF-Git Admin Mailer Subject: [28/51] [partial] cloudstack-docs git commit: Remove all old docbook files http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/f42520a5/en-US/management-server-install-overview.xml ---------------------------------------------------------------------- diff --git a/en-US/management-server-install-overview.xml b/en-US/management-server-install-overview.xml deleted file mode 100644 index 5f46b00..0000000 --- a/en-US/management-server-install-overview.xml +++ /dev/null @@ -1,48 +0,0 @@ - - -%BOOK_ENTITIES; -]> - - - -

- Management Server Installation Overview - This section describes installing the Management Server. There are two slightly different installation flows, depending on how many Management Server nodes will be in your cloud: - - A single Management Server node, with MySQL on the same node. - Multiple Management Server nodes, with MySQL on a node separate from the Management Servers. - - In either case, each machine must meet the system requirements described in System Requirements. - For the sake of security, be sure the public Internet can not access port 8096 or port 8250 on the Management Server. - The procedure for installing the Management Server is: - - - Prepare the Operating System - - - (XenServer only) Download and install vhd-util. - - Install the First Management Server - Install and Configure the MySQL database - Prepare NFS Shares - Prepare and Start Additional Management Servers (optional) - Prepare the System VM Template - -

http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/f42520a5/en-US/management-server-install-prepare-os.xml ---------------------------------------------------------------------- diff --git a/en-US/management-server-install-prepare-os.xml b/en-US/management-server-install-prepare-os.xml deleted file mode 100644 index 02453a0..0000000 --- a/en-US/management-server-install-prepare-os.xml +++ /dev/null @@ -1,54 +0,0 @@ - - -%BOOK_ENTITIES; -]> - - - -

- Prepare the Operating System - The OS must be prepared to host the Management Server using the following steps. These steps must be performed on each Management Server node. - - Log in to your OS as root. - - Check for a fully qualified hostname. - hostname --fqdn - This should return a fully qualified hostname such as "management1.lab.example.org". If it does not, edit /etc/hosts so that it does. - - - Make sure that the machine can reach the Internet. - ping www.cloudstack.org - - - Turn on NTP for time synchronization. - NTP is required to synchronize the clocks of the servers in your cloud. - - - Install NTP. - On RHEL or CentOS: - yum install ntp - On Ubuntu: - apt-get install openntpd - - - - Repeat all of these steps on every host where the Management Server will be installed. - -

http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/f42520a5/en-US/management-server-install-systemvm.xml ---------------------------------------------------------------------- diff --git a/en-US/management-server-install-systemvm.xml b/en-US/management-server-install-systemvm.xml deleted file mode 100644 index 32098b8..0000000 --- a/en-US/management-server-install-systemvm.xml +++ /dev/null @@ -1,80 +0,0 @@ - - -%BOOK_ENTITIES; -]> - - -

- Prepare the System VM Template - Secondary storage must be seeded with a template that is used for &PRODUCT; system - VMs. - - When copying and pasting a command, be sure the command has pasted as a single line before - executing. Some document viewers may introduce unwanted line breaks in copied text. - - - - On the Management Server, run one or more of the following cloud-install-sys-tmplt - commands to retrieve and decompress the system VM template. Run the command for each - hypervisor type that you expect end users to run in this Zone. - If your secondary storage mount point is not named /mnt/secondary, substitute your own - mount point name. - If you set the &PRODUCT; database encryption type to "web" when you set up the database, - you must now add the parameter -s <management-server-secret-key>. See . - This process will require approximately 5 GB of free space on the local file system and - up to 30 minutes each time it runs. - - - For Hyper-V - # /usr/share/cloudstack-common/scripts/storage/secondary/cloud-install-sys-tmplt -m /mnt/secondary -u http://download.cloud.com/templates/4.3/systemvm64template-2013-12-23-hyperv.vhd.bz2 -h hyperv -s <optional-management-server-secret-key> -F - - - For XenServer: - # /usr/lib64/cloud/common/scripts/storage/secondary/cloud-install-sys-tmplt -m /mnt/secondary -u http://download.cloud.com/templates/acton/acton-systemvm-02062012.vhd.bz2 -h xenserver -s <optional-management-server-secret-key> -F - - - For vSphere: - # /usr/lib64/cloud/common/scripts/storage/secondary/cloud-install-sys-tmplt -m /mnt/secondary -u http://download.cloud.com/templates/burbank/burbank-systemvm-08012012.ova -h vmware -s <optional-management-server-secret-key> -F - - - For KVM: - # /usr/lib64/cloud/common/scripts/storage/secondary/cloud-install-sys-tmplt -m /mnt/secondary -u http://download.cloud.com/templates/acton/acton-systemvm-02062012.qcow2.bz2 -h kvm -s <optional-management-server-secret-key> -F - - - For LXC: - # /usr/lib64/cloud/common/scripts/storage/secondary/cloud-install-sys-tmplt -m /mnt/secondary -u http://download.cloud.com/templates/acton/acton-systemvm-02062012.qcow2.bz2 -h lxc -s <optional-management-server-secret-key> -F - - - On Ubuntu, use the following path instead: - # /usr/share/cloudstack-common/scripts/storage/secondary/cloud-install-sys-tmplt - - - If you are using a separate NFS server, perform this step. If you are using the - Management Server as the NFS server, you MUST NOT perform this step. - When the script has finished, unmount secondary storage and remove the created - directory. - # umount /mnt/secondary -# rmdir /mnt/secondary - - - Repeat these steps for each secondary storage server. - - -

http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/f42520a5/en-US/management-server-lb.xml ---------------------------------------------------------------------- diff --git a/en-US/management-server-lb.xml b/en-US/management-server-lb.xml deleted file mode 100644 index 13f8756..0000000 --- a/en-US/management-server-lb.xml +++ /dev/null @@ -1,66 +0,0 @@ - - -%BOOK_ENTITIES; -]> - -

- Management Server Load Balancing - &PRODUCT; can use a load balancer to provide a virtual IP for multiple Management - Servers. The administrator is responsible for creating the load balancer rules for the - Management Servers. The application requires persistence or stickiness across multiple sessions. - The following chart lists the ports that should be load balanced and whether or not persistence - is required. - Even if persistence is not required, enabling it is permitted. - - - - - Source Port - Destination Port - Protocol - Persistence Required? - - - - - 80 or 443 - 8080 (or 20400 with AJP) - HTTP (or AJP) - Yes - - - 8250 - 8250 - TCP - Yes - - - 8096 - 8096 - HTTP - No - - - - - In addition to above settings, the administrator is responsible for setting the 'host' global - config value from the management server IP to load balancer virtual IP address. - If the 'host' value is not set to the VIP for Port 8250 and one of your management servers crashes, - the UI is still available but the system VMs will not be able to contact the management server. - -

http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/f42520a5/en-US/management-server-overview.xml ---------------------------------------------------------------------- diff --git a/en-US/management-server-overview.xml b/en-US/management-server-overview.xml deleted file mode 100644 index b8e2d53..0000000 --- a/en-US/management-server-overview.xml +++ /dev/null @@ -1,76 +0,0 @@ - - -%BOOK_ENTITIES; -]> - - - -

- Management Server Overview - - The Management Server is the &PRODUCT; software that manages cloud - resources. By interacting with the Management Server through its UI or - API, you can configure and manage your cloud infrastructure. - - - The Management Server runs on a dedicated server or VM. It controls - allocation of virtual machines to hosts and assigns storage and IP - addresses to the virtual machine instances. The Management Server - runs in a Tomcat container and requires a MySQL database for persistence. - - - The machine must meet the system requirements described in System - Requirements. - - The Management Server: - - - - - Provides the web user interface for the administrator and a - reference user interface for end users. - - - - Provides the APIs for &PRODUCT;. - - - Manages the assignment of guest VMs to particular hosts. - - - - Manages the assignment of public and private IP addresses to - particular accounts. - - - - Manages the allocation of storage to guests as virtual disks. - - - - Manages snapshots, templates, and ISO images, possibly - replicating them across data centers. - - - - Provides a single point of configuration for the cloud. - - -

http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/f42520a5/en-US/manual-live-migration.xml ---------------------------------------------------------------------- diff --git a/en-US/manual-live-migration.xml b/en-US/manual-live-migration.xml deleted file mode 100644 index 1daa6d3..0000000 --- a/en-US/manual-live-migration.xml +++ /dev/null @@ -1,56 +0,0 @@ - - -%BOOK_ENTITIES; -]> - - -

- Moving VMs Between Hosts (Manual Live Migration) - The &PRODUCT; administrator can move a running VM from one host to another without interrupting service to users or going into maintenance mode. This is called manual live migration, and can be done under the following conditions: - - The root administrator is logged in. Domain admins and users can not perform manual live migration of VMs. - The VM is running. Stopped VMs can not be live migrated. - The destination host must have enough available capacity. If not, the VM will remain in the "migrating" state until memory becomes available. - (KVM) The VM must not be using local disk storage. (On XenServer and VMware, VM live migration - with local disk is enabled by &PRODUCT; support for XenMotion and vMotion.) - (KVM) The destination host must be in the same cluster as the original host. - (On XenServer and VMware, VM live migration from one cluster to another is enabled by &PRODUCT; support for XenMotion and vMotion.) - - - To manually live migrate a virtual machine - - Log in to the &PRODUCT; UI as a user or admin. - In the left navigation, click Instances. - Choose the VM that you want to migrate. - Click the Migrate Instance button. - - - - Migrateinstance.png: button to migrate an instance - - - From the list of suitable hosts, choose the one to which you want to move the VM. - If the VM's storage has to be migrated along with the VM, this will be noted in the host - list. &PRODUCT; will take care of the storage migration for you. - - Click OK. - -

- http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/f42520a5/en-US/marvin.xml ---------------------------------------------------------------------- diff --git a/en-US/marvin.xml b/en-US/marvin.xml deleted file mode 100644 index 8fd2c96..0000000 --- a/en-US/marvin.xml +++ /dev/null @@ -1,33 +0,0 @@ - - -%BOOK_ENTITIES; -]> - - - -

- Marvin - Marvin is the &PRODUCT; automation framework. It originated as a tool for integration testing but is now also used to build DevCloud as well as to provide a Python &PRODUCT; API binding. - - Marvin's complete documenation is on the wiki at https://cwiki.apache.org/CLOUDSTACK/testing-with-python.html - The source code is located at tools/marvin - - -

http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/f42520a5/en-US/max-result-page-returned.xml ---------------------------------------------------------------------- diff --git a/en-US/max-result-page-returned.xml b/en-US/max-result-page-returned.xml deleted file mode 100644 index fdbf639..0000000 --- a/en-US/max-result-page-returned.xml +++ /dev/null @@ -1,38 +0,0 @@ - - -%BOOK_ENTITIES; -]> - - - -

- Maximum Result Pages Returned - - For each cloud, there is a default upper limit on the number of results that any API command will return in a single page. This is to help prevent overloading the cloud servers and prevent DOS attacks. For example, if the page size limit is 500 and a command returns 10,000 results, the command will return 20 pages. - - The default page size limit can be different for each cloud. It is set in the global configuration parameter default.page.size. If your cloud has many users with lots of VMs, you might need to increase the value of this parameter. At the same time, be careful not to set it so high that your site can be taken down by an enormous return from an API call. For more information about how to set global configuration parameters, see "Describe Your Deployment" in the Installation Guide. - To decrease the page size limit for an individual API command, override the global setting with the page and pagesize parameters, which are available in any list* command (listCapabilities, listDiskOfferings, etc.). - - Both parameters must be specified together. - The value of the pagesize parameter must be smaller than the value of default.page.size. That is, you can not increase the number of possible items in a result page, only decrease it. - - For syntax information on the list* commands, see the API Reference. -

- http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/f42520a5/en-US/migrate-datadisk-volume-new-storage-pool.xml ---------------------------------------------------------------------- diff --git a/en-US/migrate-datadisk-volume-new-storage-pool.xml b/en-US/migrate-datadisk-volume-new-storage-pool.xml deleted file mode 100644 index 1ed6bbd..0000000 --- a/en-US/migrate-datadisk-volume-new-storage-pool.xml +++ /dev/null @@ -1,78 +0,0 @@ - - -%BOOK_ENTITIES; -]> - - - -

- Migrating a Data Volume to a New Storage Pool - There are two situations when you might want to migrate a disk: - - Move the disk to new storage, but leave it attached to the same running VM. - Detach the disk from its current VM, move it to new storage, and attach it to a new VM. - -

- Migrating Storage For a Running VM - (Supported on XenServer and VMware) - - Log in to the &PRODUCT; UI as a user or admin. - In the left navigation bar, click Instances, click the VM name, and click View Volumes. - Click the volume you want to migrate. - Detach the disk from the VM. - See but skip the “reattach” step at the end. You - will do that after migrating to new storage. - Click the Migrate Volume button - - - - - Migrateinstance.png: button to migrate a volume - - - and choose the destination from the dropdown list. - Watch for the volume status to change to Migrating, then back to Ready. - -

- Migrating Storage and Attaching to a Different VM - - Log in to the &PRODUCT; UI as a user or admin. - Detach the disk from the VM. - See but skip the “reattach” step at the end. You - will do that after migrating to new storage. - Click the Migrate Volume button - - - - - Migrateinstance.png: button to migrate a volume - - - and choose the destination from the dropdown list. - Watch for the volume status to change to Migrating, then back to Ready. You can find the - volume by clicking Storage in the left navigation bar. Make sure that Volumes is - displayed at the top of the window, in the Select View dropdown. - Attach the volume to any desired VM running in the same cluster as the new storage server. See - - - -

http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/f42520a5/en-US/migrate-vm-rootvolume-volume-new-storage-pool.xml ---------------------------------------------------------------------- diff --git a/en-US/migrate-vm-rootvolume-volume-new-storage-pool.xml b/en-US/migrate-vm-rootvolume-volume-new-storage-pool.xml deleted file mode 100644 index 3bcaff5..0000000 --- a/en-US/migrate-vm-rootvolume-volume-new-storage-pool.xml +++ /dev/null @@ -1,47 +0,0 @@ - - -%BOOK_ENTITIES; -]> - - -

- Migrating a VM Root Volume to a New Storage Pool - (XenServer, VMware) You can live migrate a VM's root disk from one storage pool to another, without stopping the VM first. - (KVM) When migrating the root disk volume, the VM must first be stopped, and users can not access the VM. After migration is complete, the VM can be restarted. - - Log in to the &PRODUCT; UI as a user or admin. - In the left navigation bar, click Instances, and click the VM name. - (KVM only) Stop the VM. - Click the Migrate button - - - - - Migrateinstance.png: button to migrate a VM or volume - - - and choose the destination from the dropdown list. - If the VM's storage has to be migrated along with the VM, this will be noted in the host - list. &PRODUCT; will take care of the storage migration for you. - Watch for the volume status to change to Migrating, then back to Running (or Stopped, in the case of KVM). This - can take some time. - (KVM only) Restart the VM. - -

\ No newline at end of file http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/f42520a5/en-US/minimum-system-requirements.xml ---------------------------------------------------------------------- diff --git a/en-US/minimum-system-requirements.xml b/en-US/minimum-system-requirements.xml deleted file mode 100644 index b5fcf99..0000000 --- a/en-US/minimum-system-requirements.xml +++ /dev/null @@ -1,130 +0,0 @@ - - -%BOOK_ENTITIES; -]> - - -

- Minimum System Requirements -

- Management Server, Database, and Storage System Requirements - The machines that will run the Management Server and MySQL database must meet the - following requirements. The same machines can also be used to provide primary and secondary - storage, such as via localdisk or NFS. The Management Server may be placed on a virtual - machine. - - - Operating system: - - - Preferred: CentOS/RHEL 6.3+ or Ubuntu 12.04(.1) - - - - - 64-bit x86 CPU (more cores results in better performance) - - - 4 GB of memory - - - 250 GB of local disk (more results in better capability; 500 GB recommended) - - - At least 1 NIC - - - Statically allocated IP address - - - Fully qualified domain name as returned by the hostname command - - -

- Host/Hypervisor System Requirements - The host is where the cloud services run in the form of guest virtual machines. Each host - is one machine that meets the following requirements: - - - Must support HVM (Intel-VT or AMD-V enabled). - - - 64-bit x86 CPU (more cores results in better performance) - - - Hardware virtualization support required - - - 4 GB of memory - - - 36 GB of local disk - - - At least 1 NIC - - - - If DHCP is used for hosts, ensure that no conflict occurs between DHCP server used - for these hosts and the DHCP router created by &PRODUCT;. - - - - Latest hotfixes applied to hypervisor software - - - When you deploy &PRODUCT;, the hypervisor host must not have any VMs already - running - - - All hosts within a cluster must be homogeneous. The CPUs must be of the same type, - count, and feature flags. - - - Hosts have additional requirements depending on the hypervisor. See the requirements - listed at the top of the Installation section for your chosen hypervisor: - - Be sure you fulfill the additional hypervisor requirements and installation steps - provided in this Guide. Hypervisor hosts must be properly prepared to work with CloudStack. - For example, the requirements for XenServer are listed under Citrix XenServer - Installation. - - - - - - - - - - - - - - - - - - - - -

http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/f42520a5/en-US/modify-delete-service-offerings.xml ---------------------------------------------------------------------- diff --git a/en-US/modify-delete-service-offerings.xml b/en-US/modify-delete-service-offerings.xml deleted file mode 100644 index b917af4..0000000 --- a/en-US/modify-delete-service-offerings.xml +++ /dev/null @@ -1,29 +0,0 @@ - - -%BOOK_ENTITIES; -]> - - - -

- Modifying or Deleting a Service Offering - Service offerings cannot be changed once created. This applies to both compute offerings and disk offerings. - A service offering can be deleted. If it is no longer in use, it is deleted immediately and permanently. If the service offering is still in use, it will remain in the database until all the virtual machines referencing it have been deleted. After deletion by the administrator, a service offering will not be available to end users that are creating new instances. -

http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/f42520a5/en-US/multi_node_management_server.xml ---------------------------------------------------------------------- diff --git a/en-US/multi_node_management_server.xml b/en-US/multi_node_management_server.xml deleted file mode 100644 index 1ff713d..0000000 --- a/en-US/multi_node_management_server.xml +++ /dev/null @@ -1,36 +0,0 @@ - -%BOOK_ENTITIES; -]> - - -

- Multi-Node Management Server - The &PRODUCT; Management Server is deployed on one or more front-end servers connected to a single MySQL database. Optionally a pair of hardware load balancers distributes requests from the web. A backup management server set may be deployed using MySQL replication at a remote site to add DR capabilities. - - - - - Multi-Node Management Server - - The administrator must decide the following. - - Whether or not load balancers will be used. - How many Management Servers will be deployed. - Whether MySQL replication will be deployed to enable disaster recovery. - -

http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/f42520a5/en-US/multi_node_overview.xml ---------------------------------------------------------------------- diff --git a/en-US/multi_node_overview.xml b/en-US/multi_node_overview.xml deleted file mode 100644 index 1eee037..0000000 --- a/en-US/multi_node_overview.xml +++ /dev/null @@ -1,43 +0,0 @@ - - -%BOOK_ENTITIES; -]> - - - -

- Management Server Multi-Node Installation Overview - - This section describes installing multiple Management Servers and installing MySQL on a node separate from the Management Servers. The machines must meet the system requirements described in System Requirements. - - For the sake of security, be sure the public Internet can not access port 8096 or port 8250 on the Management Server. - - The procedure for a multi-node installation is: - - - Prepare the Operating System - Install the First Management Server - Install and Configure the Database - Prepare NFS Shares - Prepare and Start Additional Management Servers - Prepare the System VM Template - -

- http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/f42520a5/en-US/multi_site_deployment.xml ---------------------------------------------------------------------- diff --git a/en-US/multi_site_deployment.xml b/en-US/multi_site_deployment.xml deleted file mode 100644 index 8ad94aa..0000000 --- a/en-US/multi_site_deployment.xml +++ /dev/null @@ -1,50 +0,0 @@ - -%BOOK_ENTITIES; -]> - - -

- Multi-Site Deployment - The &PRODUCT; platform scales well into multiple sites through the use of zones. The following diagram shows an example of a multi-site deployment. - - - - - Example Of A Multi-Site Deployment - - Data Center 1 houses the primary Management Server as well as zone 1. The MySQL database is replicated in real time to the secondary Management Server installation in Data Center 2. - - - - - Separate Storage Network - - This diagram illustrates a setup with a separate storage network. Each server has four NICs, two connected to pod-level network switches and two connected to storage network switches. - There are two ways to configure the storage network: - - Bonded NIC and redundant switches can be deployed for NFS. In NFS deployments, redundant switches and bonded NICs still result in one network (one CIDR block+ default gateway address). - iSCSI can take advantage of two separate storage networks (two CIDR blocks each with its own default gateway). Multipath iSCSI client can failover and load balance between separate storage networks. - - - - - - NIC Bonding And Multipath I/O - - This diagram illustrates the differences between NIC bonding and Multipath I/O (MPIO). NIC bonding configuration involves only one network. MPIO involves two separate networks. -

http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/f42520a5/en-US/multiple-ip-nic.xml ---------------------------------------------------------------------- diff --git a/en-US/multiple-ip-nic.xml b/en-US/multiple-ip-nic.xml deleted file mode 100644 index 344dc8d..0000000 --- a/en-US/multiple-ip-nic.xml +++ /dev/null @@ -1,95 +0,0 @@ - - -%BOOK_ENTITIES; -]> - - -

- Configuring Multiple IP Addresses on a Single NIC - &PRODUCT; provides you the ability to associate multiple private IP addresses per guest VM - NIC. In addition to the primary IP, you can assign additional IPs to the guest VM NIC. This - feature is supported on all the network configurations—Basic, Advanced, and VPC. Security - Groups, Static NAT and Port forwarding services are supported on these additional IPs. - As always, you can specify an IP from the guest subnet; if not specified, an IP is - automatically picked up from the guest VM subnet. You can view the IPs associated with for each - guest VM NICs on the UI. You can apply NAT on these additional guest IPs by using network - configuration option in the &PRODUCT; UI. You must specify the NIC to which the IP should be - associated. - This feature is supported on XenServer, KVM, and VMware hypervisors. Note that Basic zone - security groups are not supported on VMware. -

- Use Cases - Some of the use cases are described below: - - - Network devices, such as firewalls and load balancers, generally work best when they - have access to multiple IP addresses on the network interface. - - - Moving private IP addresses between interfaces or instances. Applications that are - bound to specific IP addresses can be moved between instances. - - - Hosting multiple SSL Websites on a single instance. You can install multiple SSL - certificates on a single instance, each associated with a distinct IP address. - - -

- Guidelines - To prevent IP conflict, configure different subnets when multiple networks are connected - to the same VM. -

- Assigning Additional IPs to a VM - - - Log in to the &PRODUCT; UI. - - - In the left navigation bar, click Instances. - - - Click the name of the instance you want to work with. - - - In the Details tab, click NICs. - - - Click View Secondary IPs. - - - Click Acquire New Secondary IP, and click Yes in the confirmation dialog. - You need to configure the IP on the guest VM NIC manually. &PRODUCT; will not - automatically configure the acquired IP address on the VM. Ensure that the IP address - configuration persist on VM reboot. - Within a few moments, the new IP address should appear with the state Allocated. You - can now use the IP address in Port Forwarding or StaticNAT rules. - - -

- Port Forwarding and StaticNAT Services Changes - Because multiple IPs can be associated per NIC, you are allowed to select a desired IP for - the Port Forwarding and StaticNAT services. The default is the primary IP. To enable this - functionality, an extra optional parameter 'vmguestip' is added to the Port forwarding and - StaticNAT APIs (enableStaticNat, createIpForwardingRule) to indicate on what IP address NAT - need to be configured. If vmguestip is passed, NAT is configured on the specified private IP - of the VM. if not passed, NAT is configured on the primary IP of the VM. -

http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/f42520a5/en-US/multiple-ip-range.xml ---------------------------------------------------------------------- diff --git a/en-US/multiple-ip-range.xml b/en-US/multiple-ip-range.xml deleted file mode 100644 index 42e0c2a..0000000 --- a/en-US/multiple-ip-range.xml +++ /dev/null @@ -1,42 +0,0 @@ - - -%BOOK_ENTITIES; -]> - -

- About Multiple IP Ranges - - The feature can only be implemented on IPv4 addresses. - - &PRODUCT; provides you with the flexibility to add guest IP ranges from different subnets in - Basic zones and security groups-enabled Advanced zones. For security groups-enabled Advanced - zones, it implies multiple subnets can be added to the same VLAN. With the addition of this - feature, you will be able to add IP address ranges from the same subnet or from a different one - when IP address are exhausted. This would in turn allows you to employ higher number of subnets - and thus reduce the address management overhead. To support this feature, the capability of - createVlanIpRange API is extended to add IP ranges also from a different - subnet. - Ensure that you manually configure the gateway of the new subnet before adding the IP range. - Note that &PRODUCT; supports only one gateway for a subnet; overlapping subnets are not - currently supported. - Use the deleteVlanRange API to delete IP ranges. This operation fails if an IP - from the remove range is in use. If the remove range contains the IP address on which the DHCP - server is running, &PRODUCT; acquires a new IP from the same subnet. If no IP is available in - the subnet, the remove operation fails. - This feature is supported on KVM, xenServer, and VMware hypervisors. -

http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/f42520a5/en-US/multiple-system-vm-vmware.xml ---------------------------------------------------------------------- diff --git a/en-US/multiple-system-vm-vmware.xml b/en-US/multiple-system-vm-vmware.xml deleted file mode 100644 index 014dfa1..0000000 --- a/en-US/multiple-system-vm-vmware.xml +++ /dev/null @@ -1,28 +0,0 @@ - - -%BOOK_ENTITIES; -]> - - - -

- Multiple System VM Support for VMware - Every &PRODUCT; zone has single System VM for template processing tasks such as downloading templates, uploading templates, and uploading ISOs. In a zone where VMware is being used, additional System VMs can be launched to process VMware-specific tasks such as taking snapshots and creating private templates. The &PRODUCT; management server launches additional System VMs for VMware-specific tasks as the load increases. The management server monitors and weights all commands sent to these System VMs and performs dynamic load balancing and scaling-up of more System VMs. -

http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/f42520a5/en-US/network-offering-usage-record-format.xml ---------------------------------------------------------------------- diff --git a/en-US/network-offering-usage-record-format.xml b/en-US/network-offering-usage-record-format.xml deleted file mode 100644 index a1b0da9..0000000 --- a/en-US/network-offering-usage-record-format.xml +++ /dev/null @@ -1,43 +0,0 @@ - - -%BOOK_ENTITIES; -]> - - - -

- Network Offering Usage Record Format - - account – name of the account - accountid – ID of the account - domainid – ID of the domain in which this account resides - zoneid – Zone where the usage occurred - description – A string describing what the usage record is tracking - usage – String representation of the usage, including the units of usage (e.g. 'Hrs' for hours) - usagetype – A number representing the usage type (see Usage Types) - rawusage – A number representing the actual usage in hours - usageid – ID of the network offering - usagetype – A number representing the usage type (see Usage Types) - offeringid – Network offering ID - virtualMachineId – The ID of the virtual machine - virtualMachineId – The ID of the virtual machine - 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/cloudstack-docs/blob/f42520a5/en-US/network-offerings.xml ---------------------------------------------------------------------- diff --git a/en-US/network-offerings.xml b/en-US/network-offerings.xml deleted file mode 100644 index 8c685bf..0000000 --- a/en-US/network-offerings.xml +++ /dev/null @@ -1,87 +0,0 @@ - - -%BOOK_ENTITIES; -]> - - -

- Network Offerings - - For the most up-to-date list of supported network services, see the &PRODUCT; UI or call - listNetworkServices. - - A network offering is a named set of network services, such as: - - - DHCP - - - DNS - - - Source NAT - - - Static NAT - - - Port Forwarding - - - Load Balancing - - - Firewall - - - VPN - - - (Optional) Name one of several available providers to use for a given service, such as - Juniper for the firewall - - - (Optional) Network tag to specify which physical network to use - - - When creating a new VM, the user chooses one of the available network offerings, and that - determines which network services the VM can use. - The &PRODUCT; administrator can create any number of custom network offerings, in addition - to the default network offerings provided by &PRODUCT;. By creating multiple custom network - offerings, you can set up your cloud to offer different classes of service on a single - multi-tenant physical network. For example, while the underlying physical wiring may be the same - for two tenants, tenant A may only need simple firewall protection for their website, while - tenant B may be running a web server farm and require a scalable firewall solution, load - balancing solution, and alternate networks for accessing the database backend. - - If you create load balancing rules while using a network service offering that includes an - external load balancer device such as NetScaler, and later change the network service offering - to one that uses the &PRODUCT; virtual router, you must create a firewall rule on the virtual - router for each of your existing load balancing rules so that they continue to - function. - - When creating a new virtual network, the &PRODUCT; administrator chooses which network - offering to enable for that network. Each virtual network is associated with one network - offering. A virtual network can be upgraded or downgraded by changing its associated network - offering. If you do this, be sure to reprogram the physical network to match. - &PRODUCT; also has internal network offerings for use by &PRODUCT; system VMs. These network - offerings are not visible to users but can be modified by administrators. - -

http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/f42520a5/en-US/network-rate.xml ---------------------------------------------------------------------- diff --git a/en-US/network-rate.xml b/en-US/network-rate.xml deleted file mode 100644 index 56fe25c..0000000 --- a/en-US/network-rate.xml +++ /dev/null @@ -1,144 +0,0 @@ - - -%BOOK_ENTITIES; -]> - -

- Network Throttling - Network throttling is the process of controlling the network access and bandwidth usage - based on certain rules. &PRODUCT; controls this behaviour of the guest networks in the cloud by - using the network rate parameter. This parameter is defined as the default data transfer rate in - Mbps (Megabits Per Second) allowed in a guest network. It defines the upper limits for network - utilization. If the current utilization is below the allowed upper limits, access is granted, - else revoked. - You can throttle the network bandwidth either to control the usage above a certain limit for - some accounts, or to control network congestion in a large cloud environment. The network rate - for your cloud can be configured on the following: - - - Network Offering - - - Service Offering - - - Global parameter - - - If network rate is set to NULL in service offering, the value provided in the - vm.network.throttling.rate global parameter is applied. If the value is set to NULL for network - offering, the value provided in the network.throttling.rate global parameter is - considered. - For the default public, storage, and management networks, network rate is set to 0. This - implies that the public, storage, and management networks will have unlimited bandwidth by - default. For default guest networks, network rate is set to NULL. In this case, network rate is - defaulted to the global parameter value. - The following table gives you an overview of how network rate is applied on different types - of networks in &PRODUCT;. - - - - - - - Networks - Network Rate Is Taken from - - - - - Guest network of Virtual Router - Guest Network Offering - - - Public network of Virtual Router - Guest Network Offering - - - Storage network of Secondary Storage VM - System Network Offering - - - Management network of Secondary Storage VM - System Network Offering - - - Storage network of Console Proxy VM - System Network Offering - - - Management network of Console Proxy VM - System Network Offering - - - Storage network of Virtual Router - System Network Offering - - - Management network of Virtual Router - System Network Offering - - - Public network of Secondary Storage VM - System Network Offering - - - Public network of Console Proxy VM - System Network Offering - - - Default network of a guest VM - Compute Offering - - - Additional networks of a guest VM - Corresponding Network Offerings - - - - - A guest VM must have a default network, and can also have many additional networks. - Depending on various parameters, such as the host and virtual switch used, you can observe a - difference in the network rate in your cloud. For example, on a VMware host the actual network - rate varies based on where they are configured (compute offering, network offering, or both); - the network type (shared or isolated); and traffic direction (ingress or egress). - The network rate set for a network offering used by a particular network in &PRODUCT; is - used for the traffic shaping policy of a port group, for example: port group A, for that - network: a particular subnet or VLAN on the actual network. The virtual routers for that network - connects to the port group A, and by default instances in that network connects to this port - group. However, if an instance is deployed with a compute offering with the network rate set, - and if this rate is used for the traffic shaping policy of another port group for the network, - for example port group B, then instances using this compute offering are connected to the port - group B, instead of connecting to port group A. - The traffic shaping policy on standard port groups in VMware only applies to the egress - traffic, and the net effect depends on the type of network used in &PRODUCT;. In shared - networks, ingress traffic is unlimited for &PRODUCT;, and egress traffic is limited to the rate - that applies to the port group used by the instance if any. If the compute offering has a - network rate configured, this rate applies to the egress traffic, otherwise the network rate set - for the network offering applies. For isolated networks, the network rate set for the network - offering, if any, effectively applies to the ingress traffic. This is mainly because the network - rate set for the network offering applies to the egress traffic from the virtual router to the - instance. The egress traffic is limited by the rate that applies to the port group used by the - instance if any, similar to shared networks. - For example: - Network rate of network offering = 10 Mbps - Network rate of compute offering = 200 Mbps - In shared networks, ingress traffic will not be limited for &PRODUCT;, while egress traffic - will be limited to 200 Mbps. In an isolated network, ingress traffic will be limited to 10 Mbps - and egress to 200 Mbps. -

http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/f42520a5/en-US/network-service-providers.xml ---------------------------------------------------------------------- diff --git a/en-US/network-service-providers.xml b/en-US/network-service-providers.xml deleted file mode 100644 index cf86b24..0000000 --- a/en-US/network-service-providers.xml +++ /dev/null @@ -1,132 +0,0 @@ - - -%BOOK_ENTITIES; -]> - - - -

- Network Service Providers - For the most up-to-date list of supported network service providers, see the &PRODUCT; UI or call listNetworkServiceProviders. - A service provider (also called a network element) is hardware or virtual appliance that makes a network service possible; for example, a firewall appliance can be installed in the cloud to provide firewall service. On a single network, multiple providers can provide the same network service. For example, a firewall service may be provided by Cisco or Juniper devices in the same physical network. - You can have multiple instances of the same service provider in a network (say, more than one Juniper SRX device). - If different providers are set up to provide the same service on the network, the administrator can create network offerings so users can specify which network service provider they prefer (along with the other choices offered in network offerings). Otherwise, &PRODUCT; will choose which provider to use whenever the service is called for. - - Supported Network Service Providers - &PRODUCT; ships with an internal list of the supported service providers, and you can choose from this list when creating a network offering. - - - - - - - - - - - - - Virtual Router - Citrix NetScaler - Juniper SRX - F5 BigIP - Host based (KVM/Xen) - - - - - - Remote Access VPN - Yes - No - No - No - No - - - - DNS/DHCP/User Data - Yes - No - No - No - No - - - - Firewall - Yes - No - Yes - No - No - - - Load Balancing - Yes - Yes - No - Yes - No - - - Elastic IP - No - Yes - No - No - No - - - Elastic LB - No - Yes - No - No - No - - - Source NAT - Yes - No - Yes - No - No - - - Static NAT - Yes - Yes - Yes - No - No - - - Port Forwarding - Yes - No - Yes - No - No - - - - -

http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/f42520a5/en-US/network-setup.xml ---------------------------------------------------------------------- diff --git a/en-US/network-setup.xml b/en-US/network-setup.xml deleted file mode 100644 index ceee190..0000000 --- a/en-US/network-setup.xml +++ /dev/null @@ -1,35 +0,0 @@ - - -%BOOK_ENTITIES; -]> - - - Network Setup - Achieving the correct networking setup is crucial to a successful &PRODUCT; - installation. This section contains information to help you make decisions and follow the right - procedures to get your network set up correctly. - - - - - - - - - -