External Guest Load Balancer Integration (Optional)

Reply-To: dev@cloudstack.apache.org Delivered-To: mailing list commits@cloudstack.apache.org Received: (qmail 78779 invoked by uid 99); 1 Oct 2015 14:04:12 -0000 Received: from git1-us-west.apache.org (HELO git1-us-west.apache.org) (140.211.11.23) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 01 Oct 2015 14:04:12 +0000 Received: by git1-us-west.apache.org (ASF Mail Server at git1-us-west.apache.org, from userid 33) id 7ED39E1538; Thu, 1 Oct 2015 14:04:12 +0000 (UTC) Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 8bit From: sebgoa@apache.org To: commits@cloudstack.apache.org Date: Thu, 01 Oct 2015 14:04:44 -0000 Message-Id: <6a5f3d5ef25743dcbf1973760b1b860b@git.apache.org> In-Reply-To: <70dce7e46df64989b9cdbc3fddef9604@git.apache.org> References: <70dce7e46df64989b9cdbc3fddef9604@git.apache.org> X-Mailer: ASF-Git Admin Mailer Subject: [34/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/external-guest-lb-integration.xml ---------------------------------------------------------------------- diff --git a/en-US/external-guest-lb-integration.xml b/en-US/external-guest-lb-integration.xml deleted file mode 100644 index 5760f95..0000000 --- a/en-US/external-guest-lb-integration.xml +++ /dev/null @@ -1,109 +0,0 @@ - - -%BOOK_ENTITIES; -]> - -

- External Guest Load Balancer Integration (Optional) - &PRODUCT; can optionally use a Citrix NetScaler or BigIP F5 load balancer to provide load - balancing services to guests. If this is not enabled, &PRODUCT; will use the software load - balancer in the virtual router. - To install and enable an external load balancer for &PRODUCT; management: - - - Set up the appliance according to the vendor's directions. - - - Connect it to the networks carrying public traffic and management traffic (these could - be the same network). - - - Record the IP address, username, password, public interface name, and private interface - name. The interface names will be something like "1.1" or "1.2". - - - Make sure that the VLANs are trunked to the management network interface. - - - After the &PRODUCT; Management Server is installed, log in as administrator to the - &PRODUCT; UI. - - - In the left navigation bar, click Infrastructure. - - - In Zones, click View More. - - - Choose the zone you want to work with. - - - Click the Network tab. - - - In the Network Service Providers node of the diagram, click Configure. (You might have - to scroll down to see this.) - - - Click NetScaler or F5. - - - Click the Add button (+) and provide the following: - For NetScaler: - - - IP Address: The IP address of the SRX. - - - Username/Password: The authentication credentials to access the device. &PRODUCT; - uses these credentials to access the device. - - - Type: The type of device that is being added. It could be F5 Big Ip Load Balancer, - NetScaler VPX, NetScaler MPX, or NetScaler SDX. For a comparison of the NetScaler types, - see the &PRODUCT; Administration Guide. - - - Public interface: Interface of device that is configured to be part of the public - network. - - - Private interface: Interface of device that is configured to be part of the private - network. - - - Number of retries. Number of times to attempt a command on the device before - considering the operation failed. Default is 2. - - - Capacity: The number of networks the device can handle. - - - Dedicated: When marked as dedicated, this device will be dedicated to a single - account. When Dedicated is checked, the value in the Capacity field has no significance - implicitly, its value is 1. - - - - - Click OK. - - - The installation and provisioning of the external load balancer is finished. You can proceed - to add VMs and NAT or load balancing rules. -

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

- Extracting source - - Extracting the &PRODUCT; release is relatively simple and can be done - with a single command as follows: - $ tar -jxvf apache-cloudstack-4.1.0.src.tar.bz2 - - - You can now move into the directory: - $ cd ./apache-cloudstack-4.1.0-src - -

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

- What Can &PRODUCT; Do? - - Multiple Hypervisor Support - - - &PRODUCT; works with a variety of hypervisors, and a single cloud deployment can contain multiple hypervisor implementations. The current release of &PRODUCT; supports pre-packaged enterprise solutions like Citrix XenServer and VMware vSphere, as well as KVM or Xen running on Ubuntu or CentOS. - - - Massively Scalable Infrastructure Management - - - &PRODUCT; can manage tens of thousands of servers installed in multiple geographically distributed datacenters. The centralized management server scales linearly, eliminating the need for intermediate cluster-level management servers. No single component failure can cause a cloud-wide outage. Periodic maintenance of the management server can be performed without affecting the functioning of virtual machines running in the cloud. - - - Automatic Configuration Management - - &PRODUCT; automatically configures each guest virtual machine’s networking and storage settings. - - &PRODUCT; internally manages a pool of virtual appliances to support the cloud itself. These appliances offer services such as firewalling, routing, DHCP, VPN access, console proxy, storage access, and storage replication. The extensive use of virtual appliances simplifies the installation, configuration, and ongoing management of a cloud deployment. - - - Graphical User Interface - - &PRODUCT; offers an administrator's Web interface, used for provisioning and managing the cloud, as well as an end-user's Web interface, used for running VMs and managing VM templates. The UI can be customized to reflect the desired service provider or enterprise look and feel. - - - API and Extensibility - - - &PRODUCT; provides an API that gives programmatic access to all the - management features available in the UI. The API is maintained and - documented. This API enables the creation of command line tools and - new user interfaces to suit particular needs. See the Developer’s - Guide and API Reference, both available at - Apache CloudStack Guides - and - Apache CloudStack API Reference - respectively. - - - The &PRODUCT; pluggable allocation architecture allows the creation - of new types of allocators for the selection of storage and Hosts. - See the Allocator Implementation Guide - (http://docs.cloudstack.org/CloudStack_Documentation/Allocator_Implementation_Guide). - - - High Availability - - - &PRODUCT; has a number of features to increase the availability of the - system. The Management Server itself may be deployed in a multi-node - installation where the servers are load balanced. MySQL may be configured - to use replication to provide for a manual failover in the event of - database loss. For the hosts, &PRODUCT; supports NIC bonding and the use - of separate networks for storage as well as iSCSI Multipath. - -

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

- Feedback - to-do -

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

- Firewall Rules - By default, all incoming traffic to the public IP address is rejected by the firewall. To - allow external traffic, you can open firewall ports by specifying firewall rules. You can - optionally specify one or more CIDRs to filter the source IPs. This is useful when you want to - allow only incoming requests from certain IP addresses. - You cannot use firewall rules to open ports for an elastic IP address. When elastic IP is - used, outside access is instead controlled through the use of security groups. See . - In an advanced zone, you can also create egress firewall rules by using the virtual router. - For more information, see . - Firewall rules can be created using the Firewall tab in the Management Server UI. This tab - is not displayed by default when &PRODUCT; is installed. To display the Firewall tab, the - &PRODUCT; administrator must set the global configuration parameter firewall.rule.ui.enabled to - "true." - To create a firewall rule: - - - 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 work with. - - - Click the Configuration tab and fill in the following values. - - - Source CIDR. (Optional) To accept only traffic from - IP addresses within a particular address block, enter a CIDR or a comma-separated list - of CIDRs. Example: 192.168.0.0/22. Leave empty to allow all CIDRs. - - - Protocol. The communication protocol in use on the - opened port(s). - - - Start Port and End Port. The port(s) you want to - open on the firewall. If you are opening a single port, use the same number in both - fields - - - ICMP Type and ICMP Code. Used only if Protocol is - set to ICMP. Provide the type and code required by the ICMP protocol to fill out the - ICMP header. Refer to ICMP documentation for more details if you are not sure what to - enter - - - - - Click Add. - - -

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

- Install the First Management Server - - - - Ensure you have configured your machine according to - - or - - as appropriate for your platform. - - - - - Install the &PRODUCT; management server packages by - issuing one of the following commands as appropriate: - # yum install cloudstack-management - # apt-get install cloudstack-management - - - - - (RPM-based distributions) When the installation is - finished, run the following commands to start essential - services: - # service rpcbind start -# service nfs start -# chkconfig nfs on -# chkconfig rpcbind on - - - -

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

- Generic Firewall Provisions - The hardware firewall is required to serve two purposes: - - - Protect the Management Servers. NAT and port forwarding should be configured to direct - traffic from the public Internet to the Management Servers. - - - Route management network traffic between multiple zones. Site-to-site VPN should be - configured between multiple zones. - - - To achieve the above purposes you must set up fixed configurations for the firewall. - Firewall rules and policies need not change as users are provisioned into the cloud. Any brand - of hardware firewall that supports NAT and site-to-site VPN can be used. -

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

- Getting the release - - You can download the latest &PRODUCT; release from the - - Apache CloudStack project download page. - - Prior releases are available via archive.apache.org as well. See the downloads page for more information on archived releases. - You'll notice several links under the 'Latest release' section. A link to a file ending in tar.bz2, as well as a PGP/GPG signature, MD5, and SHA512 file. - - The tar.bz2 file contains the Bzip2-compressed tarball with the source code. - The .asc file is a detached cryptographic signature that can be used to help verify the authenticity of the release. - The .md5 file is an MD5 hash of the release to aid in verify the validity of the release download. - The .sha file is a SHA512 hash of the release to aid in verify the validity of the release download. - -

http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/f42520a5/en-US/global-config.xml ---------------------------------------------------------------------- diff --git a/en-US/global-config.xml b/en-US/global-config.xml deleted file mode 100644 index 626e268..0000000 --- a/en-US/global-config.xml +++ /dev/null @@ -1,354 +0,0 @@ - - -%BOOK_ENTITIES; -]> - - - Setting Configuration Parameters -

- About Configuration Parameters - &PRODUCT; provides a variety of settings you can use to set limits, configure features, - and enable or disable features in the cloud. Once your Management Server is running, you might - need to set some of these configuration parameters, depending on what optional features you - are setting up. You can set default values at the global level, which will be in effect - throughout the cloud unless you override them at a lower level. You can make local settings, - which will override the global configuration parameter values, at the level of an account, - zone, cluster, or primary storage. - The documentation for each &PRODUCT; feature should direct you to the names of the - applicable parameters. The following table shows a few of the more useful parameters. - - - - - - - Field - Value - - - - - management.network.cidr - A CIDR that describes the network that the management CIDRs reside on. This - variable must be set for deployments that use vSphere. It is recommended to be set - for other deployments as well. Example: 192.168.3.0/24. - - - xen.setup.multipath - For XenServer nodes, this is a true/false variable that instructs &PRODUCT; - to enable iSCSI multipath on the XenServer Hosts when they are added. This defaults - to false. Set it to true if you would like &PRODUCT; to enable multipath. - If this is true for a NFS-based deployment multipath will still be enabled on - the XenServer host. However, this does not impact NFS operation and is - harmless. - - - secstorage.allowed.internal.sites - This is used to protect your internal network from rogue attempts to - download arbitrary files using the template download feature. This is a - comma-separated list of CIDRs. If a requested URL matches any of these CIDRs the - Secondary Storage VM will use the private network interface to fetch the URL. Other - URLs will go through the public interface. We suggest you set this to 1 or 2 - hardened internal machines where you keep your templates. For example, set it to - 192.168.1.66/32. - - - use.local.storage - Determines whether &PRODUCT; will use storage that is local to the Host for - data disks, templates, and snapshots. By default &PRODUCT; will not use this - storage. You should change this to true if you want to use local storage and you - understand the reliability and feature drawbacks to choosing local - storage. - - - host - This is the IP address of the Management Server. If you are using multiple - Management Servers you should enter a load balanced IP address that is reachable via - the private network. - - - default.page.size - Maximum number of items per page that can be returned by a &PRODUCT; API - command. The limit applies at the cloud level and can vary from cloud to cloud. You - can override this with a lower value on a particular API call by using the page and - pagesize API command parameters. For more information, see the Developer's Guide. - Default: 500. - - - ha.tag - The label you want to use throughout the cloud to designate certain hosts - as dedicated HA hosts. These hosts will be used only for HA-enabled VMs that are - restarting due to the failure of another host. For example, you could set this to - ha_host. Specify the ha.tag value as a host tag when you add a new host to the - cloud. - - - vmware.vcenter.session.timeout - Determines the vCenter session timeout value by using this parameter. The - default value is 20 minutes. Increase the timeout value to avoid timeout errors in - VMware deployments because certain VMware operations take more than 20 - minutes. - - - - -

- Setting Global Configuration Parameters - Use the following steps to set global configuration parameters. These values will be the - defaults in effect throughout your &PRODUCT; deployment. - - - Log in to the UI as administrator. - - - In the left navigation bar, click Global Settings. - - - In Select View, choose one of the following: - - - Global Settings. This displays a list of the parameters with brief descriptions - and current values. - - - Hypervisor Capabilities. This displays a list of hypervisor versions with the - maximum number of guests supported for each. - - - - - Use the search box to narrow down the list to those you are interested in. - - - In the Actions column, click the Edit icon to modify a value. If you are viewing - Hypervisor Capabilities, you must click the name of the hypervisor first to display the - editing screen. - - -

- Setting Local Configuration Parameters - Use the following steps to set local configuration parameters for an account, zone, - cluster, or primary storage. These values will override the global configuration - settings. - - - Log in to the UI as administrator. - - - In the left navigation bar, click Infrastructure or Accounts, depending on where you - want to set a value. - - - Find the name of the particular resource that you want to work with. For example, if - you are in Infrastructure, click View All on the Zones, Clusters, or Primary Storage - area. - - - Click the name of the resource where you want to set a limit. - - - Click the Settings tab. - - - Use the search box to narrow down the list to those you are interested in. - - - In the Actions column, click the Edit icon to modify a value. - - -

- Granular Global Configuration Parameters - The following global configuration parameters have been made more granular. The parameters - are listed under three different scopes: account, cluster, and zone. - - - - - - - - Field - Field - Value - - - - - account - remote.access.vpn.client.iprange - The range of IPs to be allocated to remotely access the VPN clients. The - first IP in the range is used by the VPN server. - - - account - allow.public.user.templates - If false, users will not be able to create public templates. - - - account - use.system.public.ips - If true and if an account has one or more dedicated public IP ranges, IPs - are acquired from the system pool after all the IPs dedicated to the account have - been consumed. - - - account - use.system.guest.vlans - If true and if an account has one or more dedicated guest VLAN ranges, - VLANs are allocated from the system pool after all the VLANs dedicated to the - account have been consumed. - - - cluster - cluster.storage.allocated.capacity.notificationthreshold - The percentage, as a value between 0 and 1, of allocated storage - utilization above which alerts are sent that the storage is below the - threshold. - - - cluster - cluster.storage.capacity.notificationthreshold - The percentage, as a value between 0 and 1, of storage utilization above - which alerts are sent that the available storage is below the - threshold. - - - cluster - cluster.cpu.allocated.capacity.notificationthreshold - The percentage, as a value between 0 and 1, of cpu utilization above which - alerts are sent that the available CPU is below the threshold. - - - cluster - cluster.memory.allocated.capacity.notificationthreshold - The percentage, as a value between 0 and 1, of memory utilization above - which alerts are sent that the available memory is below the - threshold. - - - cluster - cluster.cpu.allocated.capacity.disablethreshold - The percentage, as a value between 0 and 1, of CPU utilization above which - allocators will disable that cluster from further usage. Keep the corresponding - notification threshold lower than this value to be notified - beforehand. - - - cluster - cluster.memory.allocated.capacity.disablethreshold - The percentage, as a value between 0 and 1, of memory utilization above - which allocators will disable that cluster from further usage. Keep the - corresponding notification threshold lower than this value to be notified - beforehand. - - - cluster - cpu.overprovisioning.factor - Used for CPU over-provisioning calculation; the available CPU will be the - mathematical product of actualCpuCapacity and - cpu.overprovisioning.factor. - - - cluster - mem.overprovisioning.factor - Used for memory over-provisioning calculation. - - - cluster - vmware.reserve.cpu - Specify whether or not to reserve CPU when not over-provisioning; In case - of CPU over-provisioning, CPU is always reserved. - - - cluster - vmware.reserve.mem - Specify whether or not to reserve memory when not over-provisioning; In - case of memory over-provisioning memory is always reserved. - - - zone - pool.storage.allocated.capacity.disablethreshold - The percentage, as a value between 0 and 1, of allocated storage - utilization above which allocators will disable that pool because the available - allocated storage is below the threshold. - - - zone - pool.storage.capacity.disablethreshold - The percentage, as a value between 0 and 1, of storage utilization above - which allocators will disable the pool because the available storage capacity is - below the threshold. - - - zone - storage.overprovisioning.factor - Used for storage over-provisioning calculation; available storage will be - the mathematical product of actualStorageSize and - storage.overprovisioning.factor. - - - zone - network.throttling.rate - Default data transfer rate in megabits per second allowed in a - network. - - - zone - guest.domain.suffix - Default domain name for VMs inside a virtual networks with a - router. - - - zone - router.template.xen - Name of the default router template on Xenserver. - - - zone - router.template.kvm - Name of the default router template on KVM. - - - zone - router.template.vmware - Name of the default router template on VMware. - - - zone - enable.dynamic.scale.vm - Enable or diable dynamically scaling of a VM. - - - zone - use.external.dns - Bypass internal DNS, and use the external DNS1 and DNS2 - - - zone - blacklisted.routes - Routes that are blacklisted cannot be used for creating static routes for a - VPC Private Gateway. - - - - -

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

- Globally Configured Limits - In a zone, the guest virtual network has a 24 bit CIDR by default. This limits the guest virtual network to 254 running instances. It can be adjusted as needed, but this must be done before any instances are created in the zone. For example, 10.1.1.0/22 would provide for ~1000 addresses. - The following table lists limits set in the Global Configuration: - - - - - Parameter Name - Definition - - - - - - max.account.public.ips - Number of public IP addresses that can be owned by an account - - - - max.account.snapshots - Number of snapshots that can exist for an account - - - - - max.account.templates - Number of templates that can exist for an account - - - - max.account.user.vms - Number of virtual machine instances that can exist for an account - - - - max.account.volumes - Number of disk volumes that can exist for an account - - - - max.template.iso.size - Maximum size for a downloaded template or ISO in GB - - - - max.volume.size.gb - Maximum size for a volume in GB - - - network.throttling.rate - Default data transfer rate in megabits per second allowed per user (supported on XenServer) - - - snapshot.max.hourly - Maximum recurring hourly snapshots to be retained for a volume. If the limit is reached, early snapshots from the start of the hour are deleted so that newer ones can be saved. This limit does not apply to manual snapshots. If set to 0, recurring hourly snapshots can not be scheduled - - - - snapshot.max.daily - Maximum recurring daily snapshots to be retained for a volume. If the limit is reached, snapshots from the start of the day are deleted so that newer ones can be saved. This limit does not apply to manual snapshots. If set to 0, recurring daily snapshots can not be scheduled - - - snapshot.max.weekly - Maximum recurring weekly snapshots to be retained for a volume. If the limit is reached, snapshots from the beginning of the week are deleted so that newer ones can be saved. This limit does not apply to manual snapshots. If set to 0, recurring weekly snapshots can not be scheduled - - - - snapshot.max.monthly - Maximum recurring monthly snapshots to be retained for a volume. If the limit is reached, snapshots from the beginning of the month are deleted so that newer ones can be saved. This limit does not apply to manual snapshots. If set to 0, recurring monthly snapshots can not be scheduled. - - - - - To modify global configuration parameters, use the global configuration screen in the &PRODUCT; UI. See Setting Global Configuration Parameters -

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

- Global Server Load Balancing Support - &PRODUCT; supports Global Server Load Balancing (GSLB) functionalities to provide business - continuity, and enable seamless resource movement within a &PRODUCT; environment. &PRODUCT; - achieve this by extending its functionality of integrating with NetScaler Application Delivery - Controller (ADC), which also provides various GSLB capabilities, such as disaster recovery and - load balancing. The DNS redirection technique is used to achieve GSLB in &PRODUCT;. - In order to support this functionality, region level services and service provider are - introduced. A new service 'GSLB' is introduced as a region level service. The GSLB service - provider is introduced that will provider the GSLB service. Currently, NetScaler is the - supported GSLB provider in &PRODUCT;. GSLB functionality works in an Active-Active data center - environment. -

- About Global Server Load Balancing - Global Server Load Balancing (GSLB) is an extension of load balancing functionality, which - is highly efficient in avoiding downtime. Based on the nature of deployment, GSLB represents a - set of technologies that is used for various purposes, such as load sharing, disaster - recovery, performance, and legal obligations. With GSLB, workloads can be distributed across - multiple data centers situated at geographically separated locations. GSLB can also provide an - alternate location for accessing a resource in the event of a failure, or to provide a means - of shifting traffic easily to simplify maintenance, or both. -

- Components of GSLB - A typical GSLB environment is comprised of the following components: - - - GSLB Site: In &PRODUCT; terminology, GSLB sites are - represented by zones that are mapped to data centers, each of which has various network - appliances. Each GSLB site is managed by a NetScaler appliance that is local to that - site. Each of these appliances treats its own site as the local site and all other - sites, managed by other appliances, as remote sites. It is the central entity in a GSLB - deployment, and is represented by a name and an IP address. - - - GSLB Services: A GSLB service is typically - represented by a load balancing or content switching virtual server. In a GSLB - environment, you can have a local as well as remote GSLB services. A local GSLB service - represents a local load balancing or content switching virtual server. A remote GSLB - service is the one configured at one of the other sites in the GSLB setup. At each site - in the GSLB setup, you can create one local GSLB service and any number of remote GSLB - services. - - - GSLB Virtual Servers: A GSLB virtual server refers - to one or more GSLB services and balances traffic between traffic across the VMs in - multiple zones by using the &PRODUCT; functionality. It evaluates the configured GSLB - methods or algorithms to select a GSLB service to which to send the client requests. One - or more virtual servers from different zones are bound to the GSLB virtual server. GSLB - virtual server does not have a public IP associated with it, instead it will have a FQDN - DNS name. - - - Load Balancing or Content Switching Virtual - Servers: According to Citrix NetScaler terminology, a load balancing or - content switching virtual server represents one or many servers on the local network. - Clients send their requests to the load balancing or content switching virtual server’s - virtual IP (VIP) address, and the virtual server balances the load across the local - servers. After a GSLB virtual server selects a GSLB service representing either a local - or a remote load balancing or content switching virtual server, the client sends the - request to that virtual server’s VIP address. - - - DNS VIPs: DNS virtual IP represents a load - balancing DNS virtual server on the GSLB service provider. The DNS requests for domains - for which the GSLB service provider is authoritative can be sent to a DNS VIP. - - - Authoritative DNS: ADNS (Authoritative Domain Name - Server) is a service that provides actual answer to DNS queries, such as web site IP - address. In a GSLB environment, an ADNS service responds only to DNS requests for - domains for which the GSLB service provider is authoritative. When an ADNS service is - configured, the service provider owns that IP address and advertises it. When you create - an ADNS service, the NetScaler responds to DNS queries on the configured ADNS service IP - and port. - - -

- How Does GSLB Works in &PRODUCT;? - Global server load balancing is used to manage the traffic flow to a web site hosted on - two separate zones that ideally are in different geographic locations. The following is an - illustration of how GLSB functionality is provided in &PRODUCT;: An organization, xyztelco, - has set up a public cloud that spans two zones, Zone-1 and Zone-2, across geographically - separated data centers that are managed by &PRODUCT;. Tenant-A of the cloud launches a - highly available solution by using xyztelco cloud. For that purpose, they launch two - instances each in both the zones: VM1 and VM2 in Zone-1 and VM5 and VM6 in Zone-2. Tenant-A - acquires a public IP, IP-1 in Zone-1, and configures a load balancer rule to load balance - the traffic between VM1 and VM2 instances. &PRODUCT; orchestrates setting up a virtual - server on the LB service provider in Zone-1. Virtual server 1 that is set up on the LB - service provider in Zone-1 represents a publicly accessible virtual server that client - reaches at IP-1. The client traffic to virtual server 1 at IP-1 will be load balanced across - VM1 and VM2 instances. - Tenant-A acquires another public IP, IP-2 in Zone-2 and sets up a load balancer rule to - load balance the traffic between VM5 and VM6 instances. Similarly in Zone-2, &PRODUCT; - orchestrates setting up a virtual server on the LB service provider. Virtual server 2 that - is setup on the LB service provider in Zone-2 represents a publicly accessible virtual - server that client reaches at IP-2. The client traffic that reaches virtual server 2 at IP-2 - is load balanced across VM5 and VM6 instances. At this point Tenant-A has the service - enabled in both the zones, but has no means to set up a disaster recovery plan if one of the - zone fails. Additionally, there is no way for Tenant-A to load balance the traffic - intelligently to one of the zones based on load, proximity and so on. The cloud - administrator of xyztelco provisions a GSLB service provider to both the zones. A GSLB - provider is typically an ADC that has the ability to act as an ADNS (Authoritative Domain - Name Server) and has the mechanism to monitor health of virtual servers both at local and - remote sites. The cloud admin enables GSLB as a service to the tenants that use zones 1 and - 2. - - - - - - gslb.png: GSLB architecture - - - Tenant-A wishes to leverage the GSLB service provided by the xyztelco cloud. Tenant-A - configures a GSLB rule to load balance traffic across virtual server 1 at Zone-1 and virtual - server 2 at Zone-2. The domain name is provided as A.xyztelco.com. &PRODUCT; orchestrates - setting up GSLB virtual server 1 on the GSLB service provider at Zone-1. &PRODUCT; binds - virtual server 1 of Zone-1 and virtual server 2 of Zone-2 to GLSB virtual server 1. GSLB - virtual server 1 is configured to start monitoring the health of virtual server 1 and 2 in - Zone-1. &PRODUCT; will also orchestrate setting up GSLB virtual server 2 on GSLB service - provider at Zone-2. &PRODUCT; will bind virtual server 1 of Zone-1 and virtual server 2 of - Zone-2 to GLSB virtual server 2. GSLB virtual server 2 is configured to start monitoring the - health of virtual server 1 and 2. &PRODUCT; will bind the domain A.xyztelco.com to both the - GSLB virtual server 1 and 2. At this point, Tenant-A service will be globally reachable at - A.xyztelco.com. The private DNS server for the domain xyztelcom.com is configured by the - admin out-of-band to resolve the domain A.xyztelco.com to the GSLB providers at both the - zones, which are configured as ADNS for the domain A.xyztelco.com. A client when sends a DNS - request to resolve A.xyztelcom.com, will eventually get DNS delegation to the address of - GSLB providers at zone 1 and 2. A client DNS request will be received by the GSLB provider. - The GSLB provider, depending on the domain for which it needs to resolve, will pick up the - GSLB virtual server associated with the domain. Depending on the health of the virtual - servers being load balanced, DNS request for the domain will be resolved to the public IP - associated with the selected virtual server. -

- Configuring GSLB - To configure a GSLB deployment, you must first configure a standard load balancing setup - for each zone. This enables you to balance load across the different servers in each zone in - the region. Then on the NetScaler side, configure both NetScaler appliances that you plan to - add to each zone as authoritative DNS (ADNS) servers. Next, create a GSLB site for each zone, - configure GSLB virtual servers for each site, create GLSB services, and bind the GSLB services - to the GSLB virtual servers. Finally, bind the domain to the GSLB virtual servers. The GSLB - configurations on the two appliances at the two different zones are identical, although each - sites load-balancing configuration is specific to that site. - Perform the following as a cloud administrator. As per the example given above, the - administrator of xyztelco is the one who sets up GSLB: - - - In the cloud.dns.name global parameter, specify the DNS name of your tenant's cloud - that make use of the GSLB service. - - - On the NetScaler side, configure GSLB as given in Configuring Global Server Load Balancing (GSLB): - - - Configuring a standard load balancing setup. - - - Configure Authoritative DNS, as explained in Configuring an Authoritative DNS Service. - - - Configure a GSLB site with site name formed from the domain name details. - Configure a GSLB site with the site name formed from the domain name. - As per the example given above, the site names are A.xyztelco.com and - B.xyztelco.com. - For more information, see Configuring a Basic GSLB Site. - - - Configure a GSLB virtual server. - For more information, see Configuring a GSLB Virtual Server. - - - Configure a GSLB service for each virtual server. - For more information, see Configuring a GSLB Service. - - - Bind the GSLB services to the GSLB virtual server. - For more information, see Binding GSLB Services to a GSLB Virtual Server. - - - Bind domain name to GSLB virtual server. Domain name is obtained from the domain - details. - For more information, see Binding a Domain to a GSLB Virtual Server. - - - - - In each zone that are participating in GSLB, add GSLB-enabled NetScaler device. - For more information, see . - - - As a domain administrator/ user perform the following: - - - Add a GSLB rule on both the sites. - See . - - - Assign load balancer rules. - See . - - -

- Prerequisites and Guidelines - - - The GSLB functionality is supported both Basic and Advanced zones. - - - GSLB is added as a new network service. - - - GSLB service provider can be added to a physical network in a zone. - - - The admin is allowed to enable or disable GSLB functionality at region level. - - - The admin is allowed to configure a zone as GSLB capable or enabled. - A zone shall be considered as GSLB capable only if a GSLB service provider is - provisioned in the zone. - - - When users have VMs deployed in multiple availability zones which are GSLB enabled, - they can use the GSLB functionality to load balance traffic across the VMs in multiple - zones. - - - The users can use GSLB to load balance across the VMs across zones in a region only - if the admin has enabled GSLB in that region. - - - The users can load balance traffic across the availability zones in the same region - or different regions. - - - The admin can configure DNS name for the entire cloud. - - - The users can specify an unique name across the cloud for a globally load balanced - service. The provided name is used as the domain name under the DNS name associated with - the cloud. - The user-provided name along with the admin-provided DNS name is used to produce a - globally resolvable FQDN for the globally load balanced service of the user. For - example, if the admin has configured xyztelco.com as the DNS name for the cloud, and - user specifies 'foo' for the GSLB virtual service, then the FQDN name of the GSLB - virtual service is foo.xyztelco.com. - - - While setting up GSLB, users can select a load balancing method, such as round - robin, for using across the zones that are part of GSLB. - - - The user shall be able to set weight to zone-level virtual server. Weight shall be - considered by the load balancing method for distributing the traffic. - - - The GSLB functionality shall support session persistence, where series of client - requests for particular domain name is sent to a virtual server on the same zone. - Statistics is collected from each GSLB virtual server. - - -

- Enabling GSLB in NetScaler - In each zone, add GSLB-enabled NetScaler device for load balancing. - - - Log in as administrator to the &PRODUCT; UI. - - - In the left navigation bar, click Infrastructure. - - - In Zones, click View More. - - - Choose the zone you want to work with. - - - Click the Physical Network tab, then click the name of the physical network. - - - In the Network Service Providers node of the diagram, click Configure. - You might have to scroll down to see this. - - - Click NetScaler. - - - Click Add NetScaler device and provide the following: - For NetScaler: - - - IP Address: The IP address of the SDX. - - - Username/Password: The authentication - credentials to access the device. &PRODUCT; uses these credentials to access the - device. - - - Type: The type of device that is being added. - It could be F5 Big Ip Load Balancer, NetScaler VPX, NetScaler MPX, or NetScaler SDX. - For a comparison of the NetScaler types, see the &PRODUCT; Administration - Guide. - - - Public interface: Interface of device that is - configured to be part of the public network. - - - Private interface: Interface of device that is - configured to be part of the private network. - - - GSLB service: Select this option. - - - GSLB service Public IP: The public IP address - of the NAT translator for a GSLB service that is on a private network. - - - GSLB service Private IP: The private IP of the - GSLB service. - - - Number of Retries. Number of times to attempt a - command on the device before considering the operation failed. Default is 2. - - - Capacity: The number of networks the device can - handle. - - - Dedicated: When marked as dedicated, this - device will be dedicated to a single account. When Dedicated is checked, the value - in the Capacity field has no significance implicitly, its value is 1. - - - - - Click OK. - - -

- Adding a GSLB Rule - - - Log in to the &PRODUCT; UI as a domain administrator or user. - - - In the left navigation pane, click Region. - - - Select the region for which you want to create a GSLB rule. - - - In the Details tab, click View GSLB. - - - Click Add GSLB. - The Add GSLB page is displayed as follows: - - - - - - gslb-add.png: adding a gslb rule - - - - - Specify the following: - - - Name: Name for the GSLB rule. - - - Description: (Optional) A short description of - the GSLB rule that can be displayed to users. - - - GSLB Domain Name: A preferred domain name for - the service. - - - Algorithm: (Optional) The algorithm to use to - load balance the traffic across the zones. The options are Round Robin, Least - Connection, and Proximity. - - - Service Type: The transport protocol to use for - GSLB. The options are TCP and UDP. - - - Domain: (Optional) The domain for which you - want to create the GSLB rule. - - - Account: (Optional) The account on which you - want to apply the GSLB rule. - - - - - Click OK to confirm. - - -

- Assigning Load Balancing Rules to GSLB - - - Log in to the &PRODUCT; UI as a domain administrator or user. - - - In the left navigation pane, click Region. - - - Select the region for which you want to create a GSLB rule. - - - In the Details tab, click View GSLB. - - - Select the desired GSLB. - - - Click view assigned load balancing. - - - Click assign more load balancing. - - - Select the load balancing rule you have created for the zone. - - - Click OK to confirm. - - -

- Known Limitation - Currently, &PRODUCT; does not support orchestration of services across the zones. The - notion of services and service providers in region are to be introduced. -

http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/f42520a5/en-US/gsoc-dharmesh.xml ---------------------------------------------------------------------- diff --git a/en-US/gsoc-dharmesh.xml b/en-US/gsoc-dharmesh.xml deleted file mode 100644 index 5e2bf73..0000000 --- a/en-US/gsoc-dharmesh.xml +++ /dev/null @@ -1,149 +0,0 @@ - - -%BOOK_ENTITIES; -]> - - - - - Dharmesh's 2013 GSoC Proposal - This chapter describes Dharmrsh's 2013 Google Summer of Code project within the &PRODUCT; ASF project. It is a copy paste of the submitted proposal. -

- Abstract - - The project aims to bring cloudformation like service to cloudstack. One of the prime use-case is cluster computing frameworks on cloudstack. A cloudformation service will give users and administrators of cloudstack ability to manage and control a set of resources easily. The cloudformation will allow booting and configuring a set of VMs and form a cluster. Simple example would be LAMP stack. More complex clusters such as mesos or hadoop cluster requires a little more advanced configuration. There is already some work done by Chiradeep Vittal at this front [5]. In this project, I will implement server side cloudformation service for cloudstack and demonstrate how to run mesos cluster using it. - -

- -

- Mesos - - Mesos is a resource management platform for clusters. It aims to increase resource utilization of clusters by sharing cluster resources among multiple processing frameworks(like MapReduce, MPI, Graph Processing) or multiple instances of same framework. It provides efficient resource isolation through use of containers. Uses zookeeper for state maintenance and fault tolerance. - -

- -

- What can run on mesos ? - - Spark: A cluster computing framework based on the Resilient Distributed Datasets (RDDs) abstraction. RDD is more generalized than MapReduce and can support iterative and interactive computation while retaining fault tolerance, scalability, data locality etc. - - Hadoop:: Hadoop is fault tolerant and scalable distributed computing framework based on MapReduce abstraction. - - Begel:: A graph processing framework based on pregel. - - and other frameworks like MPI, Hypertable. -

- -

- How to deploy mesos ? - - Mesos provides cluster installation scripts for cluster deployment. There are also scripts available to deploy a cluster on Amazon EC2. It would be interesting to see if this scripts can be leveraged in anyway. -

- -

- Deliverables - - - Deploy CloudStack and understand instance configuration/contextualization - - - Test and deploy Mesos on a set of CloudStack based VM, manually. Design/propose an automation framework - - - Test stackmate and engage chiradeep (report bugs, make suggestion, make pull request) - - - Create cloudformation template to provision a Mesos Cluster - - - Compare with Apache Whirr or other cluster provisioning tools for server side implementation of cloudformation service. - - -

- -

- Architecture and Tools - - The high level architecture is as follows: - - - - - - - - - - - It includes following components: - - - - CloudFormation Query API server: - This acts as a point of contact to and exposes CloudFormation functionality as Query API. This can be accessed directly or through existing tools from Amazon AWS for their cloudformation service. It will be easy to start as a module which resides outside cloudstack at first and I plan to use dropwizard [3] to start with. Later may be the API server can be merged with cloudstack core. I plan to use mysql for storing details of clusters. - - - - Provisioning: - - Provisioning module is responsible for handling the booting process of the VMs through cloudstack. This uses the cloudstack APIs for launching VMs. I plan to use preconfigured templates/images with required dependencies installed, which will make cluster creation process much faster even for large clusters. Error handling is very important part of this module. For example, what you do if few VMs fail to boot in cluster ? - - - - Configuration: - - This module deals with configuring the VMs to form a cluster. This can be done via manual scripts/code or via configuration management tools like chef/ironfan/knife. Potentially workflow automation tools like rundeck [4] also can be used. Also Apache whirr and Provisionr are options. I plan to explore this tools and select suitable ones. - - - -

- -

- API - - Query API will be based on Amazon AWS cloudformation service. This will allow leveraging existing tools for AWS. -

- -

- Timeline - 1-1.5 week : project design. Architecture, tools selection, API design - 1-1.5 week : getting familiar with cloudstack and stackmate codebase and architecture details - 1-1.5 week : getting familiar with mesos internals - 1-1.5 week : setting up the dev environment and create mesos templates - 2-3 week : build provisioning and configuration module - Midterm evaluation: provisioning module, configuration module - 2-3 week : develope cloudformation server side implementation - 2-3 week : test and integrate -

- -

- Future Work - - - Auto Scaling: - Automatically adding or removing VMs from mesos cluster based on various conditions like utilization going above/below a static threshold. There can be more sophisticated strategies based on prediction or fine grained metric collection with tight integration with mesos framework. - - - Cluster Simulator: - Integrating with existing simulator to simulate mesos clusters. This can be useful in various scenarios, for example while developing a new scheduling algorithm, testing autoscaling etc. - - -