Return-Path: X-Original-To: apmail-incubator-cloudstack-dev-archive@minotaur.apache.org Delivered-To: apmail-incubator-cloudstack-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id A7B18D5EE for ; Tue, 11 Sep 2012 14:41:54 +0000 (UTC) Received: (qmail 81372 invoked by uid 500); 11 Sep 2012 14:41:54 -0000 Delivered-To: apmail-incubator-cloudstack-dev-archive@incubator.apache.org Received: (qmail 81334 invoked by uid 500); 11 Sep 2012 14:41:54 -0000 Mailing-List: contact cloudstack-dev-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-dev@incubator.apache.org Received: (qmail 81325 invoked by uid 99); 11 Sep 2012 14:41:54 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 11 Sep 2012 14:41:54 +0000 X-ASF-Spam-Status: No, hits=1.0 required=5.0 tests=FILL_THIS_FORM_SHORT,RCVD_IN_DNSWL_LOW,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (athena.apache.org: local policy) Received: from [209.85.216.175] (HELO mail-qc0-f175.google.com) (209.85.216.175) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 11 Sep 2012 14:41:49 +0000 Received: by qcad10 with SMTP id d10so325706qca.6 for ; Tue, 11 Sep 2012 07:41:28 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type:content-transfer-encoding:x-gm-message-state; bh=qoBV3rXOmSCM7LhgvdOKItMhlTIoZUGaO4AIUTWWt08=; b=MsHRI/Ye47pXKA3VVtl0kwgRRHiDgQ+KcX6Z+eR2o1A7J1LLFwfBfs4G+LInY6GW6l DCOeqlqsxjIyaJNkBxrJNsvlY5xevvtyG/9aZVDZQvRlyZTFfu6KKpPhvC9q6kM0dtXc UGYejjwbn1bEl4l2r0EMTNEvgiAtWosFDyOVlJMXsat0mx8akyJ7VwZl/3nWn2mN8b2j 1smjrrxuVrSRG9W4WRgdMr0dAmea5X9icxI8tklSPkMOaRjZSwoFoaIP5J8jFvKhkcXG +h8Z2Nk8bN+wUIEsL2i8U0yd4wDbOSFw7a/ZEMEH1A0JRQsE63GGhfstabcKVrEP4Y/g mM5w== Received: by 10.224.183.79 with SMTP id cf15mr18730873qab.16.1347374488529; Tue, 11 Sep 2012 07:41:28 -0700 (PDT) MIME-Version: 1.0 Received: by 10.49.12.19 with HTTP; Tue, 11 Sep 2012 07:41:08 -0700 (PDT) In-Reply-To: <20120911085533.ADAF3355F0@tyr.zones.apache.org> References: <20120911085533.ADAF3355F0@tyr.zones.apache.org> From: David Nalley Date: Tue, 11 Sep 2012 10:41:08 -0400 Message-ID: Subject: Re: [1/9] git commit: Feature Documentation for s2svpn interVlan and Autoscale To: cloudstack-dev@incubator.apache.org Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable X-Gm-Message-State: ALoCoQkPne3Sa2MADSK6KW2e6kMwZqHNenmPmEAorYgUtgrZAQG3JLRrFOQdCJkzaFvrYn2vFj0w X-Virus-Checked: Checked by ClamAV on apache.org Unfortunately this seems to have broken the docs build. FATAL ERROR: XInclude:1604 in developer-guide.xml on line 32: could not load contacting-support.xml, and no fallback was found at /usr/bin/publican line 763 It's comparatively trivial to build the docs before committing, please try and do that if at all possible, and if not possible consider deferring committing. Also - this commit has a number of style problems, tabs were introduced instead of using spaces, and changes were made to 149 different files (which should have been a warning sign in and of itself since this is supposedly only about s2svpn, vpc, and a feature not yet present.) Pranav: do you want to fix this in place or would you consider reverting it= ? On Tue, Sep 11, 2012 at 4:55 AM, wrote: > Updated Branches: > refs/heads/master 87ecde648 -> 4a8bb9dfc > > > Feature Documentation for s2svpn interVlan and Autoscale > > > Project: http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/repo > Commit: http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/commi= t/4a8bb9df > Tree: http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/tree/4a= 8bb9df > Diff: http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/diff/4a= 8bb9df > > Branch: refs/heads/master > Commit: 4a8bb9dfc70a1d0b1b855b10d821a54ed51a0ba6 > Parents: 87ecde6 > Author: Radhika Puthiyetath > Authored: Tue Sep 11 14:23:59 2012 +0530 > Committer: Pranav Saxena > Committed: Tue Sep 11 14:23:59 2012 +0530 > > ---------------------------------------------------------------------- > docs/en-US/LDAPserver-for-user-authentication.xml | 33 +- > docs/en-US/about-clusters.xml | 2 +- > docs/en-US/about-hosts.xml | 34 +- > docs/en-US/about-physical-networks.xml | 38 +- > docs/en-US/about-pods.xml | 41 +- > docs/en-US/about-primary-storage.xml | 2 +- > docs/en-US/about-secondary-storage.xml | 2 +- > docs/en-US/about-virtual-networks.xml | 39 +- > docs/en-US/about-working-with-vms.xml | 54 +- > docs/en-US/about-zones.xml | 37 +- > docs/en-US/accessing-vms.xml | 66 ++- > docs/en-US/accounts-users-domains.xml | 31 +- > docs/en-US/accounts.xml | 35 +- > docs/en-US/add-additional-guest-network.xml | 70 ++-- > docs/en-US/add-ingress-egress-rules.xml | 123 +++-- > docs/en-US/add-iso.xml | 178 ++++--- > docs/en-US/add-load-balancer-rule.xml | 84 ++-- > docs/en-US/add-security-group.xml | 54 +- > docs/en-US/advanced-zone-configuration.xml | 437 +++++++++-----= - > docs/en-US/advanced-zone-guest-ip-addresses.xml | 33 +- > docs/en-US/advanced-zone-network-traffic-types.xml | 35 +- > ...dvanced-zone-physical-network-configuration.xml | 39 +- > docs/en-US/advanced-zone-public-ip-addresses.xml | 33 +- > docs/en-US/alerts.xml | 96 ++-- > docs/en-US/attach-iso-to-vm.xml | 59 +- > .../automatic-snapshot-creation-retention.xml | 47 +- > docs/en-US/basic-zone-configuration.xml | 39 +- > docs/en-US/basic-zone-guest-ip-addresses.xml | 35 +- > docs/en-US/basic-zone-network-traffic-types.xml | 35 +- > .../basic-zone-physical-network-configuration.xml | 38 +- > docs/en-US/best-practices-for-vms.xml | 55 ++- > .../change-network-offering-on-guest-network.xml | 77 ++-- > docs/en-US/changing-root-password.xml | 37 +- > docs/en-US/changing-secondary-storage-ip.xml | 74 ++-- > docs/en-US/changing-service-offering-for-vm.xml | 83 ++-- > docs/en-US/changing-vm-name-os-group.xml | 95 ++-- > docs/en-US/cloud-infrastructure-concepts.xml | 50 +- > docs/en-US/cloud-infrastructure-overview.xml | 75 ++-- > docs/en-US/cloudstack_admin.xml | 59 ++- > docs/en-US/cluster-add.xml | 39 +- > docs/en-US/compute-disk-service-offerings.xml | 40 +- > docs/en-US/concepts.xml | 41 +- > .../configure-guest-traffic-in-advanced-zone.xml | 88 ++-- > docs/en-US/configure-usage-server.xml | 47 +- > docs/en-US/configure-vpn.xml | 87 ++-- > docs/en-US/console-proxy.xml | 33 +- > docs/en-US/convert-hyperv-vm-to-template.xml | 117 ++-- > docs/en-US/create-template-from-existing-vm.xml | 87 ++-- > docs/en-US/create-template-from-snapshot.xml | 38 +- > docs/en-US/create-templates-overview.xml | 52 +- > docs/en-US/create-windows-template.xml | 58 +- > docs/en-US/creating-compute-offerings.xml | 74 ++- > docs/en-US/creating-network-offerings.xml | 122 +++-- > docs/en-US/creating-new-volumes.xml | 88 ++-- > docs/en-US/creating-vms.xml | 86 ++-- > docs/en-US/default-account-resource-limit.xml | 53 +- > docs/en-US/deleting-vms.xml | 66 ++- > docs/en-US/deployment-architecture-overview.xml | 69 ++-- > docs/en-US/detach-move-volumes.xml | 71 ++-- > docs/en-US/developer-guide.xml | 39 +- > docs/en-US/enable-disable-static-nat.xml | 70 ++-- > docs/en-US/enable-security-groups.xml | 39 +- > docs/en-US/end-user-ui-overview.xml | 37 +- > docs/en-US/event-log-queries.xml | 33 +- > docs/en-US/event-types.xml | 425 +++++++------- > docs/en-US/events-log.xml | 43 +- > docs/en-US/events.xml | 31 +- > .../external-firewalls-and-load-balancers.xml | 38 +- > docs/en-US/feature-overview.xml | 117 ++-- > docs/en-US/firewall-rules.xml | 91 ++-- > docs/en-US/globally-configured-limits.xml | 178 +++--- > docs/en-US/guest-traffic.xml | 55 +- > docs/en-US/ha-for-hosts.xml | 35 +- > docs/en-US/host-add.xml | 48 +- > docs/en-US/host-allocation.xml | 33 +- > .../hypervisor-support-for-primarystorage.xml | 183 +++--- > docs/en-US/images/cluster-overview.png | Bin 6973 -> 6080 b= ytes > docs/en-US/import-ami.xml | 108 ++-- > docs/en-US/initialize-and-test.xml | 102 ++-- > docs/en-US/ip-forwarding-firewalling.xml | 34 +- > docs/en-US/isolated-networks.xml | 33 +- > docs/en-US/linux-installation.xml | 82 ++-- > docs/en-US/load-balancer-rules.xml | 37 +- > docs/en-US/log-in-root-admin.xml | 34 +- > docs/en-US/log-in.xml | 44 +- > docs/en-US/maintain-hypervisors-on-hosts.xml | 33 +- > docs/en-US/manage-cloud.xml | 45 +- > docs/en-US/manual-live-migration.xml | 83 ++-- > ...grate-vm-rootvolume-volume-new-storage-pool.xml | 54 +- > docs/en-US/minimum-system-requirements.xml | 153 +++--- > docs/en-US/network-offerings.xml | 46 +- > docs/en-US/network-service-providers.xml | 133 ++++- > docs/en-US/networking-in-a-pod.xml | 69 ++- > docs/en-US/networking-in-a-zone.xml | 56 +- > docs/en-US/networking-overview.xml | 51 +- > docs/en-US/pod-add.xml | 51 ++- > docs/en-US/port-forwarding.xml | 80 ++-- > docs/en-US/primary-storage-add.xml | 60 ++- > docs/en-US/primary-storage.xml | 42 +- > docs/en-US/projects.xml | 53 +- > docs/en-US/provisioning-steps-overview.xml | 70 ++-- > docs/en-US/provisioning-steps.xml | 36 +- > docs/en-US/release-ip-address.xml | 64 ++- > docs/en-US/removing-vsphere-hosts.xml | 32 +- > ...untime-allocation-virtual-network-resources.xml | 37 +- > ...cheduled-maintenance-maintenance-mode-hosts.xml | 34 +- > docs/en-US/secondary-storage-add.xml | 41 +- > docs/en-US/secondary-storage-vm.xml | 41 +- > docs/en-US/secondary-storage.xml | 38 +- > docs/en-US/security-groups.xml | 36 +- > docs/en-US/set-up-invitations.xml | 53 +- > docs/en-US/set-up-network-for-users.xml | 46 +- > docs/en-US/set-usage-limit.xml | 36 +- > docs/en-US/shared-networks.xml | 38 +- > docs/en-US/site-to-site-vpn.xml | 72 ++-- > docs/en-US/standard-events.xml | 35 +- > docs/en-US/static-nat.xml | 34 +- > docs/en-US/stop-restart-management-server.xml | 33 +- > docs/en-US/stopping-and-starting-vms.xml | 7 +- > docs/en-US/storage.xml | 43 +- > docs/en-US/suspend-project.xml | 48 +- > docs/en-US/sys-reliability-and-ha.xml | 45 +- > docs/en-US/sysprep-for-windows-server-2003R2.xml | 96 ++-- > docs/en-US/sysprep-windows-server-2008R2.xml | 48 +- > docs/en-US/system-reserved-ip-addresses.xml | 36 +- > docs/en-US/system-service-offerings.xml | 34 +- > docs/en-US/time-zones.xml | 259 +++++----- > docs/en-US/troubleshooting.xml | 52 +- > docs/en-US/tuning.xml | 36 +- > docs/en-US/ui.xml | 35 +- > docs/en-US/upload-template.xml | 100 ++-- > docs/en-US/user-services-overview.xml | 119 +--- > docs/en-US/using-multiple-guest-networks.xml | 43 +- > docs/en-US/using-sshkeys.xml | 95 ++-- > docs/en-US/vcenter-maintenance-mode.xml | 36 +- > docs/en-US/virtual-router.xml | 35 +- > docs/en-US/vm-lifecycle.xml | 63 +- > docs/en-US/vm-storage-migration.xml | 44 +- > docs/en-US/vpc.xml | 160 +++++-- > docs/en-US/vpn.xml | 58 ++- > docs/en-US/windows-installation.xml | 37 +- > docs/en-US/work-with-usage.xml | 47 +- > docs/en-US/working-with-hosts.xml | 51 +- > docs/en-US/working-with-iso.xml | 43 +- > docs/en-US/working-with-snapshots.xml | 49 +- > docs/en-US/working-with-system-vm.xml | 39 +- > docs/en-US/working-with-templates.xml | 44 +- > docs/en-US/working-with-volumes.xml | 46 +- > docs/en-US/xenserver-maintenance-mode.xml | 40 +- > 149 files changed, 5092 insertions(+), 4360 deletions(-) > ---------------------------------------------------------------------- > > > http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/4a8bb9df= /docs/en-US/LDAPserver-for-user-authentication.xml > ---------------------------------------------------------------------- > diff --git a/docs/en-US/LDAPserver-for-user-authentication.xml b/docs/en-= US/LDAPserver-for-user-authentication.xml > index 5fcb300..376631c 100644 > --- a/docs/en-US/LDAPserver-for-user-authentication.xml > +++ b/docs/en-US/LDAPserver-for-user-authentication.xml > @@ -5,23 +5,22 @@ > ]> > > > - >
> Using an LDAP Server for User Authentication > You can use an external LDAP server such as Microsoft Active D= irectory or ApacheDS to authenticate &PRODUCT; end-users. Just map &PRODUCT= ; accounts to the corresponding LDAP accounts using a query filter. The que= ry filter is written using the query syntax of the particular LDAP server, = and can include special wildcard characters provided by &PRODUCT; for match= ing common values such as the user=92s email address and name. &PRODUCT; wi= ll search the external LDAP directory tree starting at a specified base dir= ectory and return the distinguished name (DN) and password of the matching = user. This information along with the given password is used to authenticat= e the user.. > @@ -37,4 +36,4 @@ > > > > -
> + > > http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/4a8bb9df= /docs/en-US/about-clusters.xml > ---------------------------------------------------------------------- > diff --git a/docs/en-US/about-clusters.xml b/docs/en-US/about-clusters.xm= l > index e328cba..b01fcfc 100644 > --- a/docs/en-US/about-clusters.xml > +++ b/docs/en-US/about-clusters.xml > @@ -1,5 +1,5 @@ > > - + > %BOOK_ENTITIES; > ]> > > http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/4a8bb9df= /docs/en-US/about-hosts.xml > ---------------------------------------------------------------------- > diff --git a/docs/en-US/about-hosts.xml b/docs/en-US/about-hosts.xml > index 956c695..2002a6a 100644 > --- a/docs/en-US/about-hosts.xml > +++ b/docs/en-US/about-hosts.xml > @@ -1,25 +1,25 @@ > > - + > %BOOK_ENTITIES; > ]> > > > >
> @@ -28,7 +28,7 @@ > The host is the smallest organizational unit within a &PRODUCT= ; deployment. Hosts are contained within clusters, clusters are contained w= ithin pods, and pods are contained within zones. > Hosts in a &PRODUCT; deployment: > > - Provde the CPU, memory, storage, and networking = resources needed to host the virtual machines > + Provide the CPU, memory, storage, and networking= resources needed to host the virtual machines > Interconnect using a high bandwidth TCP/IP netwo= rk and connect to the Internet > May reside in multiple data centers across diffe= rent geographic locations > May have different capacities (different CPU spe= eds, different amounts of RAM, etc.), although the hosts within a cluster m= ust all be homogeneous > > http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/4a8bb9df= /docs/en-US/about-physical-networks.xml > ---------------------------------------------------------------------- > diff --git a/docs/en-US/about-physical-networks.xml b/docs/en-US/about-ph= ysical-networks.xml > index 8edb9e0..b22e48b 100644 > --- a/docs/en-US/about-physical-networks.xml > +++ b/docs/en-US/about-physical-networks.xml > @@ -1,29 +1,28 @@ > > - + > %BOOK_ENTITIES; > ]> > > > - >
> - About Physical Networks > + About Physical Networks > Part of adding a zone is setting up the physical network. One = or (in an advanced zone) more physical networks can be associated with each= zone. The network corresponds to a NIC on the hypervisor host. Each physic= al network can carry one or more types of network traffic. The choices of t= raffic type for each network vary depending on whether you are creating a z= one with basic networking or advanced networking. > A physical network is the actual network hardware and wiring i= n a zone. A zone can have multiple physical networks. An administrator can:= > > @@ -33,8 +32,7 @@ > Configure the service providers (firewalls, load= balancers, etc.) available on a physical network > Configure the IP addresses trunked to a physical= network > Specify what type of traffic is carried on the p= hysical network, as well as other properties like network speed > - > - > + > > > > > http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/4a8bb9df= /docs/en-US/about-pods.xml > ---------------------------------------------------------------------- > diff --git a/docs/en-US/about-pods.xml b/docs/en-US/about-pods.xml > index ed3520c..57ae1a3 100644 > --- a/docs/en-US/about-pods.xml > +++ b/docs/en-US/about-pods.xml > @@ -1,33 +1,34 @@ > > - + > %BOOK_ENTITIES; > ]> > > > >
> About Pods > - A pod often represents a single rack. Hosts in the same pod ar= e in the same subnet. > - A pod is the second-largest organizational unit within a &PROD= UCT; deployment. Pods are contained within zones. Each zone can contain one= or more pods. > - Pods are not visible to the end user. > - A pod consists of one or more clusters of hosts and one or mor= e primary storage servers. > + A pod often represents a single rack. Hosts in the same pod ar= e in the same subnet. > + A pod is the second-largest organizational unit within a &PRODUC= T; deployment. Pods are contained within zones. Each zone can contain one o= r more pods. > + A pod consists of one or more clusters of hosts and one or more = primary storage servers. > + Pods are not visible to the end user. > + > > > > > http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/4a8bb9df= /docs/en-US/about-primary-storage.xml > ---------------------------------------------------------------------- > diff --git a/docs/en-US/about-primary-storage.xml b/docs/en-US/about-prim= ary-storage.xml > index 68d7a25..a9cf054 100644 > --- a/docs/en-US/about-primary-storage.xml > +++ b/docs/en-US/about-primary-storage.xml > @@ -1,5 +1,5 @@ > > - + > %BOOK_ENTITIES; > ]> > > http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/4a8bb9df= /docs/en-US/about-secondary-storage.xml > ---------------------------------------------------------------------- > diff --git a/docs/en-US/about-secondary-storage.xml b/docs/en-US/about-se= condary-storage.xml > index c4df0b8..c5b4f5d 100644 > --- a/docs/en-US/about-secondary-storage.xml > +++ b/docs/en-US/about-secondary-storage.xml > @@ -1,5 +1,5 @@ > > - + > %BOOK_ENTITIES; > ]> > > http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/4a8bb9df= /docs/en-US/about-virtual-networks.xml > ---------------------------------------------------------------------- > diff --git a/docs/en-US/about-virtual-networks.xml b/docs/en-US/about-vir= tual-networks.xml > index 2fc6ba9..225717e 100644 > --- a/docs/en-US/about-virtual-networks.xml > +++ b/docs/en-US/about-virtual-networks.xml > @@ -5,27 +5,26 @@ > ]> > > > - >
> About Virtual Networks > - A virtual network is a logical construct that enables multi-te= nancy on a single physical network. In &PRODUCT;, a virtual network can be = shared or isolated. > - XenServer and Maintenanc= e Mode > - Working with Usage > - XenServer and Maintenance Mode > + A virtual network is a logical construct that enables multi-te= nancy on a single physical network. In &PRODUCT; a virtual network can be s= hared or isolated. > + > + > + >
> > http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/4a8bb9df= /docs/en-US/about-working-with-vms.xml > ---------------------------------------------------------------------- > diff --git a/docs/en-US/about-working-with-vms.xml b/docs/en-US/about-wor= king-with-vms.xml > index 47153e2..259c61b 100644 > --- a/docs/en-US/about-working-with-vms.xml > +++ b/docs/en-US/about-working-with-vms.xml > @@ -5,35 +5,35 @@ > ]> > > > >
> - About Working with Virtual Machines > - &PRODUCT; provides administrators with complete control ov= er the lifecycle of all guest VMs executing in the cloud. &PRODUCT; provide= s several guest management operations for end users and administrators. VMs= may be stopped, started, rebooted, and destroyed. > - Guest VMs have a name and group. VM names and groups are o= paque to &PRODUCT; and are available for end users to organize their VMs. E= ach VM can have three names for use in different contexts. Only two of thes= e names can be controlled by the user: > - > - Instance name – a unique, immutable ID= that is generated by &PRODUCT; and can not be modified by the user. This n= ame conforms to the requirements in IETF RFC 1123. > - Display name – the name displayed in t= he &PRODUCT; web UI. Can be set by the user. Defaults to instance name. > - Name – host name that the DHCP server = assigns to the VM. Can be set by the user. Defaults to instance name= > - > - Guest VMs can be configured to be Highly Available (HA). A= n HA-enabled VM is monitored by the system. If the system detects that the = VM is down, it will attempt to restart the VM, possibly on a different host= . For more information, see HA-Enabled Virtual Machines on > - Each new VM is allocated one public IP address. When the V= M is started, &PRODUCT; automatically creates a static NAT between this pub= lic IP address and the private IP address of the VM. > - If elastic IP is in use (with the NetScaler load balancer)= , the IP address initially allocated to the new VM is not marked as elastic= . The user must replace the automatically configured IP with a specifically= acquired elastic IP, and set up the static NAT mapping between this new IP= and the guest VM=92s private IP. The VM=92s original IP address is then re= leased and returned to the pool of available public IPs. > - &PRODUCT; cannot distinguish a guest VM that was shut down= by the user (such as with the =93shutdown=94 command in Linux) from a VM t= hat shut down unexpectedly. If an HA-enabled VM is shut down from inside th= e VM, &PRODUCT; will restart it. To shut down an HA-enabled VM, you must go= through the &PRODUCT; UI or API. > + About Working with Virtual Machines > + &PRODUCT; provides administrators with complete control ove= r the lifecycle of all guest VMs executing in the cloud. &PRODUCT; provides= several guest management operations for end users and administrators. VMs = may be stopped, started, rebooted, and destroyed. > + Guest VMs have a name and group. VM names and groups are op= aque to &PRODUCT; and are available for end users to organize their VMs. Ea= ch VM can have three names for use in different contexts. Only two of these= names can be controlled by the user: > + > + Instance name =96 a unique, immut= able ID that is generated by &PRODUCT;, and can not be modified by the user= . This name conforms to the requirements in IETF RFC 1123. > + Display name =96 the name display= ed in the &PRODUCT; web UI. Can be set by the user. Defaults to instance na= me. > + Name =96 host name that the DHCP = server assigns to the VM. Can be set by the user. Defaults to instance name= > + > + Guest VMs can be configured to be Highly Available = (HA). An HA-enabled VM is monitored by the system. If the system detects th= at the VM is down, it will attempt to restart the VM, possibly on a differe= nt host. For more information, see HA-Enabled Virtual Machines on > + Each new VM is allocated one public IP address. Whe= n the VM is started, &PRODUCT; automatically creates a static NAT between t= his public IP address and the private IP address of the VM. > + If elastic IP is in use (with the NetScaler load ba= lancer), the IP address initially allocated to the new VM is not marked as = elastic. The user must replace the automatically configured IP with a speci= fically acquired elastic IP, and set up the static NAT mapping between this= new IP and the guest VM=92s private IP. The VM=92s original IP address is = then released and returned to the pool of available public IPs. > + &PRODUCT; cannot distinguish a guest VM that was sh= ut down by the user (such as with the =93shutdown=94 command in Linux) from= a VM that shut down unexpectedly. If an HA-enabled VM is shut down from in= side the VM, &PRODUCT; will restart it. To shut down an HA-enabled VM, you = must go through the &PRODUCT; UI or API. >
> > > http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/4a8bb9df= /docs/en-US/about-zones.xml > ---------------------------------------------------------------------- > diff --git a/docs/en-US/about-zones.xml b/docs/en-US/about-zones.xml > index a05a9a6..5385df0 100644 > --- a/docs/en-US/about-zones.xml > +++ b/docs/en-US/about-zones.xml > @@ -1,29 +1,28 @@ > > - + > %BOOK_ENTITIES; > ]> > > > - >
> - About Zones > + About Zones > A zone is the largest organizational unit within a &PRODUCT; d= eployment. A zone typically corresponds to a single datacenter, although it= is permissible to have multiple zones in a datacenter. The benefit of orga= nizing infrastructure into zones is to provide physical isolation and redun= dancy. For example, each zone can have its own power supply and network upl= ink, and the zones can be widely separated geographically (though this is n= ot required). > A zone consists of: > > @@ -34,7 +33,7 @@ > > > > - zone-overview.png: Nested structure of a sim= ple zone > + zone-overview.png: Nested structure of a sim= ple zone. > > Zones are visible to the end user. When a user starts a guest = VM, the user must select a zone for their guest. Users might also be requir= ed to copy their private templates to additional zones to enable creation o= f guest VMs using their templates in those zones. > Zones can be public or private. Public zones are visible to a= ll users. This means that any user may create a guest in that zone. Priva= te zones are reserved for a specific domain. Only users in that domain or = its subdomains may create guests in that zone. > > http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/4a8bb9df= /docs/en-US/accessing-vms.xml > ---------------------------------------------------------------------- > diff --git a/docs/en-US/accessing-vms.xml b/docs/en-US/accessing-vms.xml > index d69d021..7053996 100644 > --- a/docs/en-US/accessing-vms.xml > +++ b/docs/en-US/accessing-vms.xml > @@ -5,37 +5,43 @@ > ]> > > > - >
> - Accessing VMs > - Any user can access their own virtual machines. The administra= tor can access all VMs running in the cloud. > - To access a VM through the &PRODUCT; UI: > - > - Log in to the &PRODUCT; UI as a user or admi= n. > - Click Instances, then click the name of a ru= nning VM. > - Click the View Console button . > - > - To access a VM directly over the network: > - > - The VM must have some port open to incoming = traffic. For example, in a basic zone, a new VM might be assigned to a secu= rity group which allows incoming traffic. This depends on what security gro= up you picked when creating the VM. In other cases, you can open a port by = setting up a port forwarding policy. See IP Forwarding and Firewalling. > - If a port is open but you can not access the= VM using ssh, it=92s possible that ssh is not already enabled on the VM. T= his will depend on whether ssh is enabled in the template you picked when c= reating the VM. Access the VM through the &PRODUCT; UI and enable ssh on th= e machine using the commands for the VM=92s operating system. > - If the network has an external firewall devi= ce, you will need to create a firewall rule to allow access. See IP Forward= ing and Firewalling. > - > + Accessing VMs > + Any user can access their own virtual machines. The adminis= trator can access all VMs running in the cloud. > + To access a VM through the &PRODUCT; UI: > + > + Log in to the &PRODUCT; UI as a u= ser or admin. > + Click Instances, then click the n= ame of a running VM. > + Click the View Console > + > + > + > + > + consoleicon.png: button t= o view the console. > + > + > + > + To access a VM directly over the network: > + > + The VM must have some port open t= o incoming traffic. For example, in a basic zone, a new VM might be assigne= d to a security group which allows incoming traffic. This depends on what s= ecurity group you picked when creating the VM. In other cases, you can open= a port by setting up a port forwarding policy. See IP Forwarding and Firew= alling. > + If a port is open but you can not= access the VM using ssh, it=92s possible that ssh is not already enabled o= n the VM. This will depend on whether ssh is enabled in the template you pi= cked when creating the VM. Access the VM through the &PRODUCT; UI and enabl= e ssh on the machine using the commands for the VM=92s operating system. > + If the network has an external fi= rewall device, you will need to create a firewall rule to allow access. See= IP Forwarding and Firewalling. > + >
> > > http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/4a8bb9df= /docs/en-US/accounts-users-domains.xml > ---------------------------------------------------------------------- > diff --git a/docs/en-US/accounts-users-domains.xml b/docs/en-US/accounts-= users-domains.xml > index 8549129..a3f5837 100644 > --- a/docs/en-US/accounts-users-domains.xml > +++ b/docs/en-US/accounts-users-domains.xml > @@ -5,23 +5,22 @@ > ]> > > > - >
> Accounts, Users, and Domains > > > http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/4a8bb9df= /docs/en-US/accounts.xml > ---------------------------------------------------------------------- > diff --git a/docs/en-US/accounts.xml b/docs/en-US/accounts.xml > index 5292a9c..aa62f68 100644 > --- a/docs/en-US/accounts.xml > +++ b/docs/en-US/accounts.xml > @@ -5,24 +5,25 @@ > ]> > > > > -
> + > + Accounts > > > -
> + > > http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/4a8bb9df= /docs/en-US/add-additional-guest-network.xml > ---------------------------------------------------------------------- > diff --git a/docs/en-US/add-additional-guest-network.xml b/docs/en-US/add= -additional-guest-network.xml > index 57e7ffd..3d3858a 100644 > --- a/docs/en-US/add-additional-guest-network.xml > +++ b/docs/en-US/add-additional-guest-network.xml > @@ -5,39 +5,43 @@ > ]> > > > - >
> - Adding an Additional Guest Network > - > - Log in to the &PRODUCT; UI as an administrator o= r end user. > - In the left navigation, choose Network > - Click Add guest network. Provide the following i= nformation: > - > - Name. The name of the network. This wil= l be user-visible. > - Description. The description of the netw= ork. This will be user-visible. > - Network offering. If the administrator h= as configured multiple network offerings, select the one you want to use fo= r this network. > - Pod. The name of the pod this network ap= plies to. Each pod in a basic zone is a broadcast domain, and therefore eac= h pod has a different IP range for the guest network. The administrator mus= t configure the IP range for each pod. > - VLAN ID. The VLAN tag for this network.<= /para> > - Gateway. The gateway that the guests sho= uld use. > - Netmask. The netmask in use on the subne= t the guests will use. > - Start IP/End IP. Enter the first and las= t IP addresses that define a range that &PRODUCT; can assign to guests. We= strongly recommend the use of multiple NICs. If multiple NICs are used, th= ey may be in a different subnet. If one NIC is used, these IPs should be i= n the same CIDR as the pod CIDR. > - Click Create. > - > + Adding an Additional Guest Network > + > + Log in to the &PRODUCT; UI as an administ= rator or end user. > + In the left navigation, choose Network. > + Click Add guest network. Provide the foll= owing information: > + > + N= ame: The name of the network. This will be user-visible. = > + D= isplay Text: The description of the network. This will be > + user-visible. > + Z= one. The name of the zone this network applies to. Each zone is = a broadcast domain, and therefore each zone has a different > + IP range for the guest network. T= he administrator must configure the IP > + range for each zone. > + N= etwork offering: If the administrator has configured > + multiple network offering= s, select the one you want to use for this > + network. > + G= uest Gateway: The gateway that the guests should use. > + G= uest Netmask: The netmask in use on the subnet the guests will > + use. > + > + Click Create. > + > > -
> +
> > http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/4a8bb9df= /docs/en-US/add-ingress-egress-rules.xml > ---------------------------------------------------------------------- > diff --git a/docs/en-US/add-ingress-egress-rules.xml b/docs/en-US/add-ing= ress-egress-rules.xml > index 964045f..10895d6 100644 > --- a/docs/en-US/add-ingress-egress-rules.xml > +++ b/docs/en-US/add-ingress-egress-rules.xml > @@ -5,55 +5,88 @@ > ]> > > > >
> Adding Ingress and Egress Rules to a Security Group > - > + > Log in to the &PRODUCT; UI as an administrator o= r end user. > In the left navigation, choose Network > - In Select view, choose Security Groups, then cli= ck the security group you want . > - To add an ingress rule, click the Ingress Rules = tab and fill out the following fields to specify what network traffic is al= lowed into VM instances in this security group. If no ingress rules are spe= cified, then no traffic will be allowed in, except for responses to any tra= ffic that has been allowed out through an egress rule. > - > - Add by CIDR/Account<= /emphasis>. Indicate whether the source of the traffic will be defined by I= P address (CIDR) or an existing security group in a &PRODUCT; account (Acco= unt). Choose Account if you want to allow incoming traffic from all VMs in = another security group > - Protocol.= The networking protocol that sources will use to send traffic to the secur= ity group. TCP and UDP are typically used for data exchange and end-user co= mmunications. ICMP is typically used to send error messages or network moni= toring data. > - Start Port, End Port= . (TCP, UDP only) A range of listening ports that are the destin= ation for the incoming traffic. If you are opening a single port, use the s= ame number in both fields. > - ICMP Type, ICMP = Code. (ICMP only) The type of message and error code that will b= e accepted. > - CIDR. (Ad= d by CIDR only) To accept only traffic from IP addresses within a particula= r address block, enter a CIDR or a comma-separated list of CIDRs. The CIDR = is the base IP address of the incoming traffic. For example, 192.168.0.0/22= . To allow all CIDRs, set to 0.0.0.0/0. > - Account, Security Gr= oup. (Add by Account only) To accept only traffic from another s= ecurity group, enter the &PRODUCT; account and name of a security group tha= t has already been defined in that account. To allow traffic between VMs wi= thin the security group you are editing now, enter the same name you used i= n step 7. > - > - The following example allows inbound HTTP access from = anywhere: > - > - > - > - > - httpaccess.png: allows inbound HTTP = access from anywhere > - > - > - To add an egress rule, click the Egress Rules ta= b and fill out the following fields to specify what type of traffic is allo= wed to be sent out of VM instances in this security group. If no egress rul= es are specified, then all traffic will be allowed out. Once egress rules a= re specified, the following types of traffic are allowed out: traffic speci= fied in egress rules; queries to DNS and DHCP servers; and responses to any= traffic that has been allowed in through an ingress rule > - > - Add by CIDR/Account<= /emphasis>. Indicate whether the destination of the traffic will be defined= by IP address (CIDR) or an existing security group in a &PRODUCT; account = (Account). Choose Account if you want to allow outgoing traffic to all VMs = in another security group. > - Protocol.= The networking protocol that VMs will use to send outgoing traffic. TCP an= d UDP are typically used for data exchange and end-user communications. ICM= P is typically used to send error messages or network monitoring data. > - Start Port, End Port= . (TCP, UDP only) A range of listening ports that are the destin= ation for the outgoing traffic. If you are opening a single port, use the s= ame number in both fields. > - ICMP Type, ICMP Code= . (ICMP only) The type of message and error code that will be se= nt > - CIDR. (Ad= d by CIDR only) To send traffic only to IP addresses within a particular ad= dress block, enter a CIDR or a comma-separated list of CIDRs. The CIDR is t= he base IP address of the destination. For example, 192.168.0.0/22. To allo= w all CIDRs, set to 0.0.0.0/0. > - Account, Security Gr= oup. (Add by Account only) To allow traffic to be sent to anothe= r security group, enter the &PRODUCT; account and name of a security group = that has already been defined in that account. To allow traffic between VMs= within the security group you are editing now, enter its name. > - > - Click Add. > - > + In Select view, choose Security Groups, t= hen click the security group you want . > + To add an ingress rule, click the Ingress= Rules tab and fill out the following fields to specify what network traffi= c is allowed into VM instances in this security group. If no ingress rules = are specified, then no traffic will be allowed in, except for responses to = any traffic that has been allowed out through an egress rule. > + > + Add by CI= DR/Account. Indicate whether the source of the > + traffic will be defined b= y IP address (CIDR) or an existing security group > + in a &PRODUCT; account (A= ccount). Choose Account if you want to allow > + incoming traffic from all= VMs in another security group > + Protocol<= /emphasis>. The networking protocol that sources will use to > + send traffic to the secur= ity group. TCP and UDP are typically used for data > + exchange and end-user com= munications. ICMP is typically used to send error > + messages or network monit= oring data. > + Start Por= t, End Port. (TCP, UDP only) A range of listening > + ports that are the destin= ation for the incoming traffic. If you are opening > + a single port, use the sa= me number in both fields. > + I= CMP Type, ICMP Code. (ICMP only) The type of message and > + error code that will be a= ccepted. > + CIDR. (Add by CIDR only) To accept only traffic from IP > + addresses within a partic= ular address block, enter a CIDR or a > + comma-separated list of C= IDRs. The CIDR is the base IP address of the > + incoming traffic. For exa= mple, 192.168.0.0/22. To allow all CIDRs, set to > + 0.0.0.0/0. > + Account, = Security Group. (Add by Account only) To accept only > + traffic from another secu= rity group, enter the &PRODUCT; account and > + name of a security group = that has already been defined in that account. To > + allow traffic between VMs= within the security group you are editing now, > + enter the same name you u= sed in step 7. > + > + The following example allows inbound HTTP a= ccess from anywhere: > + > + > + > + > + httpaccess.png: allow= s inbound HTTP access from anywhere > + > + > + To add an egress rule, click the Egress R= ules tab and fill out the following fields to specify what type of traffic = is allowed to be sent out of VM instances in this security group. If no egr= ess rules are specified, then all traffic will be allowed out. Once egress = rules are specified, the following types of traffic are allowed out: traffi= c specified in egress rules; queries to DNS and DHCP servers; and responses= to any traffic that has been allowed in through an ingress rule > + > + Add by CI= DR/Account. Indicate whether the destination of the > + traffic will be defined b= y IP address (CIDR) or an existing security group > + in a &PRODUCT; account (A= ccount). Choose Account if you want to allow > + outgoing traffic to all V= Ms in another security group. > + Protocol<= /emphasis>. The networking protocol that VMs will use to send > + outgoing traffic. TCP and= UDP are typically used for data exchange and > + end-user communications. = ICMP is typically used to send error messages or > + network monitoring data.<= /para> > + Start Por= t, End Port. (TCP, UDP only) A range of listening > + ports that are the destin= ation for the outgoing traffic. If you are opening > + a single port, use the sa= me number in both fields. > + ICMP Type= , ICMP Code. (ICMP only) The type of message and > + error code that will be s= ent > + CIDR. (Add by CIDR only) To send traffic only to IP addresses > + within a particular addre= ss block, enter a CIDR or a comma-separated list of > + CIDRs. The CIDR is the ba= se IP address of the destination. For example, > + 192.168.0.0/22. To allow = all CIDRs, set to 0.0.0.0/0. > + Account, = Security Group. (Add by Account only) To allow > + traffic to be sent to ano= ther security group, enter the &PRODUCT; > + account and name of a sec= urity group that has already been defined in that > + account. To allow traffic= between VMs within the security group you are > + editing now, enter its na= me. > + > + Click Add. > + >
> > http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/4a8bb9df= /docs/en-US/add-iso.xml > ---------------------------------------------------------------------- > diff --git a/docs/en-US/add-iso.xml b/docs/en-US/add-iso.xml > index f56d10c..60f6116 100644 > --- a/docs/en-US/add-iso.xml > +++ b/docs/en-US/add-iso.xml > @@ -5,87 +5,103 @@ > ]> > > > - >
> - Adding an ISO > - To make additional operating system or other software availabl= e for use with guest VMs, you can add an ISO. The ISO is typically thought = of as an operating system image, but you can also add ISOs for other types = of software, such as desktop applications that you want to be installed as = part of a template. > - > - Log in to the &PRODUCT; UI as an administrator o= r end user. > - In the left navigation bar, click Templates. > - In Select View, choose ISOs. > - Click Add ISO. > - In the Add ISO screen, provide the following: > - > - Name. Short name for the ISO image. (E.g. Ce= ntOS 6.2 64 bit). > - Description. Display test for the ISO image.= (E.g. CentOS 6.2 64 bit). > - URL. The URL that hosts the ISO image. The M= anagement Server must be able to access this location via HTTP. If needed y= ou can place the ISO image directly on the Management Server > - Zone. Choose the zone where you want the ISO= to be available, or All Zones to make it available throughout &PRODUCT;. > - Bootable. Whether or not a guest could boot = off this ISO image. For example, a CentOS ISO is bootable, a Microsoft Off= ice ISO is not bootable. > - OS Type. This helps &PRODUCT; and the hyperv= isor perform certain operations and make assumptions that improve the perfo= rmance of the guest. Select one of the following. > - > - If the operating system of your desi= red ISO image is listed, choose it. > - If the OS Type of the ISO is not lis= ted or if the ISO is not bootable, choose Other. > - (XenServer only) If you want to boot= from this ISO in PV mode, choose Other PV (32-bit) or Other PV (64-bit) > - (KVM only) If you choose an OS that = is PV-enabled, the VMs created from this ISO will have a SCSI (virtio) root= disk. If the OS is not PV-enabled, the VMs will have an IDE root disk. The= PV-enabled types are: > - > - > - > - > - Fedora 13 > - Fedora 12 > - Fedora 11 > - > - > - > - Fedora 10 > - Fedora 9 > - Other PV > - > - > - > - Debian GNU/Linux > - CentOS 5.3 > - CentOS 5.4 > - > - > - CentOS 5.5 > - Red Hat Enterprise = Linux 5.3 > - Red Hat Enterprise = Linux 5.4 > - > - > - Red Hat Enterprise Linu= x 5.5 > - Red Hat Enterprise Linu= x 6 > - > - > - > - > - > - > - Note: It is not recommended to choose an old= er version of the OS than the version in the image. For example, choosing C= entOS 5.4 to support a CentOS 6.2 image will usually not work. In these cas= es, choose Other. > - > - Extractable. Choose Yes if the ISO should be= available for extraction. > - Public. Choose Yes if this ISO should be ava= ilable to other users. > - Featured. Choose Yes if you would like this = ISO to be more prominent for users to select. The ISO will appear in the Fe= atured ISOs list. Only an administrator can make an ISO Featured. > - > - Click OK. > - The Management Server will download the ISO. Depending= on the size of the ISO, this may take a long time. The ISO status column w= ill display Ready once it has been successfully downloaded into secondary s= torage. Clicking Refresh updates the download percentage. > - > - Important: Wa= it for the ISO to finish downloading. If you move on to the next task and t= ry to use the ISO right away, it will appear to fail. The entire ISO must = be available before &PRODUCT; can work with it > - > + Adding an ISO > + To make additional operating system or other software avail= able for use with guest VMs, you can add an ISO. The ISO is typically thoug= ht of as an operating system image, but you can also add ISOs for other typ= es of software, such as desktop applications that you want to be installed = as part of a template. > + > + Log in to the &PRODUCT; UI as an administ= rator or end user. > + In the left navigation bar, click Templat= es. > + In Select View, choose ISOs. > + Click Add ISO. > + In the Add ISO screen, provide the follow= ing: > + > + Name: Short name for the ISO image. For example, CentOS 6.2 > + 64-bit. > + Descripti= on: Display test for the ISO image. For example, > + CentOS 6.2 64-bit.= > + URL: The URL that hosts the ISO image. The Management Server > + must be able to access th= is location via HTTP. If needed you can place the > + ISO image directly on the= Management Server > + Zone: Choose the zone where you want the ISO to be available, > + or All Zones to make it a= vailable throughout &PRODUCT;. > + Bootable<= /emphasis>: Whether or not a guest could boot off this ISO > + image. For example, a Cen= tOS ISO is bootable, a Microsoft Office ISO is not > + bootable. > + OS Type: This helps &PRODUCT; and the hypervisor perform > + certain operations and ma= ke assumptions that improve the performance of the > + guest. Select one of the = following. > + > + If the operating = system of your desired ISO image is listed, choose it. > + If the OS Type of= the ISO is not listed or if the ISO is not bootable, choose Other.<= /listitem> > + (XenServer only) = If you want to boot from this ISO in PV mode, choose Other PV (32-bit) or O= ther PV (64-bit) > + (KVM only) If you= choose an OS that is PV-enabled, the VMs created from this ISO will have a= SCSI (virtio) root disk. If the OS is not PV-enabled, the VMs will have an= IDE root disk. The PV-enabled types are: > + > + > + > + <= row> > + = Fedora 13 > + = Fedora 12 > + = Fedora 11 > + > + <= /row> > + <= row> > + <= entry>Fedora 10 > + <= entry>Fedora 9 > + = Other PV > + > + <= /row> > + <= row> > + = Debian GNU/Linux > + = CentOS 5.3 > + = CentOS 5.4 > + <= /row> > + <= row> > + = CentOS 5.5 > + = Red Hat Enterprise Linux 5.3 > + = Red Hat Enterprise Linux 5.4 > + <= /row> > + > + <= entry>Red Hat Enterprise Linux 5.5 > + <= entry>Red Hat Enterprise Linux 6 > + <= entry> > + > + > + > + > + > + It is not recommended to choo= se an older version of the OS than the version in the image. For > + example, choosing= CentOS 5.4 to support a CentOS 6.2 image will usually > + not work. In thes= e cases, choose Other. > + > + Extractab= le: Choose Yes if the ISO should be available for > + extraction. > + Public: Choose Yes if this ISO should be available to other > + users. > + Featured<= /emphasis>: Choose Yes if you would like this ISO to be more > + prominent for users to se= lect. The ISO will appear in the Featured ISOs > + list. Only an administrat= or can make an ISO Featured. > + > + Click OK. > + The Management Server will download the ISO= . Depending on the size of the ISO, this may take a long time. The ISO stat= us column will display Ready once it has been successfully downloaded into = secondary storage. Clicking Refresh updates the download percentage. > + > + Important: Wait for the ISO to finish downloading. If you > + move on to the next task and try to use t= he ISO right away, it will appear to fail. > + The entire ISO must be available before &= PRODUCT; can work with it. > + >
> > http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/4a8bb9df= /docs/en-US/add-load-balancer-rule.xml > ---------------------------------------------------------------------- > diff --git a/docs/en-US/add-load-balancer-rule.xml b/docs/en-US/add-load-= balancer-rule.xml > index ddbce95..30128ef 100644 > --- a/docs/en-US/add-load-balancer-rule.xml > +++ b/docs/en-US/add-load-balancer-rule.xml > @@ -5,42 +5,56 @@ > ]> > > > >
> - Adding a Load Balancer Rule > - > - Log in to the &PRODUCT; UI as an administrator o= r end user. > - In the left navigation, choose Network. > - Click the name of the network where you want to = load balance the traffic. > - Click View IP Addresses. > - Click the IP address for which you want to creat= e the rule, then click the Configuration tab. > - In the Load Balancing node of the diagram, click= View All. > - Fill in the following: > - > - Name. A name for the load balancer rule. > - Public Port. The port receiving incoming tra= ffic to be balanced. > - Private Port. The port that the VMs will use= to receive the traffic. > - Algorithm. Choose the load balancing algorit= hm you want &PRODUCT; to use. &PRODUCT; supports a variety of well-known al= gorithms. If you are not familiar with these choices, you will find plenty = of information about them on the Internet. > - Stickiness. (Optional) Click Configure and c= hoose the algorithm for the stickiness policy. See Sticky Session Policies = for Load Balancer Rules. > - > - Click Add VMs, then select two or more VMs that = will divide the load of incoming traffic, and click Apply. > - The new load balancer rule appears in the list. You can re= peat these steps to add more load balancer rules for this IP address. > - > - > + Adding a Load Balancer Rule > + > + Log in to the &PRODUCT; UI as an administ= rator or end user. > + In the left navigation, choose Network. > + Click the name of the network where you w= ant to load balance the traffic. > + Click View IP Addresses. > + Click the IP address for which you want t= o create the rule, then click the Configuration tab. > + In the Load Balancing node of the diagram= , click View All. > + In a Basic zone, you can also create a load balanci= ng rule without acquiring or selecting an > + IP address. &PRODUCT; internally assign a= n IP when you create the load balancing > + rule, which is listed in the IP Addresses= page when the rule is created. > + To do that, select the name of the network, then cl= ick Add Load Balancer tab. Continue with > + . > + Fill in the following: > + > + Name: A name for the load balancer rule. > + Public Po= rt: The port receiving incoming traffic to be > + balanced. > + Private P= ort: The port that the VMs will use to receive the > + traffic. > + Algorithm= : Choose the load balancing algorithm you want > + &PRODUCT; to use. &PRODUC= T; supports a variety of well-known > + algorithms. If you are no= t familiar with these choices, you will find plenty > + of information about them= on the Internet. > + Stickines= s: (Optional) Click Configure and choose the > + algorithm for the stickin= ess policy. See Sticky Session Policies for Load > + Balancer Rules. > + AutoScale= : Click Configure and complete the AutoScale > + configuration as explaine= d in . > + > + Click Add VMs, then select two or more VM= s that will divide the load of incoming traffic, and click Apply. > + The new load balancer rule appears in the list. You= can repeat these steps to add more load balancer rules for this IP address= . > + > + >
>