You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cloudstack.apache.org by pa...@apache.org on 2018/07/27 13:17:14 UTC
[cloudstack-documentation] 01/01: initial commit of new layout/consolidated documentation

This is an automated email from the ASF dual-hosted git repository.

paul_a pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/cloudstack-documentation.git

commit 70858617a0968bd04ade7a3a8a51c6215978a8a3
Author: Paul Angus <pa...@shapeblue.com>
AuthorDate: Fri Jul 27 14:15:54 2018 +0100

    initial commit of new layout/consolidated documentation
---
 Makefile                                           |   20 +
 make.bat                                           |   36 +
 source/_global.rst                                 |   46 +
 source/_static/acslogo.png                         |  Bin 0 -> 135394 bytes
 source/_static/images/1000-foot-view.png           |  Bin 0 -> 222230 bytes
 source/_static/images/60recipe.gif                 |  Bin 0 -> 19564 bytes
 source/_static/images/CloudStack-ldap-screen1.png  |  Bin 0 -> 23243 bytes
 source/_static/images/DevCloud-hostonly.png        |  Bin 0 -> 39311 bytes
 source/_static/images/DevCloud.png                 |  Bin 0 -> 33529 bytes
 source/_static/images/SnapshotButton.png           |  Bin 0 -> 967 bytes
 source/_static/images/VMSnapshotButton.png         |  Bin 0 -> 967 bytes
 source/_static/images/acslogo.png                  |  Bin 0 -> 135394 bytes
 source/_static/images/add-cifs.png                 |  Bin 0 -> 15692 bytes
 source/_static/images/add-cluster.png              |  Bin 0 -> 35697 bytes
 source/_static/images/add-gateway.png              |  Bin 0 -> 16360 bytes
 source/_static/images/add-gslb.png                 |  Bin 0 -> 17665 bytes
 source/_static/images/add-guest-network.png        |  Bin 0 -> 20547 bytes
 source/_static/images/add-ip-range.png             |  Bin 0 -> 16572 bytes
 .../_static/images/add-ldap-configuration-ad.png   |  Bin 0 -> 70112 bytes
 .../images/add-ldap-configuration-openldap.png     |  Bin 0 -> 65270 bytes
 source/_static/images/add-new-gateway-vpc.png      |  Bin 0 -> 21912 bytes
 source/_static/images/add-tier.png                 |  Bin 0 -> 19054 bytes
 source/_static/images/add-vlan-icon.png            |  Bin 0 -> 860 bytes
 source/_static/images/add-vm-vpc.png               |  Bin 0 -> 8596 bytes
 source/_static/images/add-vpc.png                  |  Bin 0 -> 20392 bytes
 source/_static/images/add-vpn-customer-gateway.png |  Bin 0 -> 29851 bytes
 source/_static/images/addAccount-icon.png          |  Bin 0 -> 605 bytes
 source/_static/images/addvm-tier-sharednw.png      |  Bin 0 -> 111465 bytes
 source/_static/images/attach-disk-icon.png         |  Bin 0 -> 1092 bytes
 source/_static/images/autoscale-config.png         |  Bin 0 -> 39379 bytes
 source/_static/images/basic-deployment.png         |  Bin 0 -> 5892 bytes
 source/_static/images/change-admin-password.png    |  Bin 0 -> 141860 bytes
 source/_static/images/change-affinity-button.png   |  Bin 0 -> 7300 bytes
 source/_static/images/change-password.png          |  Bin 0 -> 891 bytes
 source/_static/images/change-service-icon.png      |  Bin 0 -> 769 bytes
 source/_static/images/cifs-primary.png             |  Bin 0 -> 32016 bytes
 source/_static/images/cifs-ss.png                  |  Bin 0 -> 33303 bytes
 source/_static/images/cloudian-s3_ss_cache.png     |  Bin 0 -> 69503 bytes
 source/_static/images/cloudian-s3_ss_config.png    |  Bin 0 -> 45092 bytes
 source/_static/images/cloudian-ss_globalopt.png    |  Bin 0 -> 71861 bytes
 source/_static/images/cloudian-tab.png             |  Bin 0 -> 6122 bytes
 source/_static/images/cluster-overview.png         |  Bin 0 -> 6080 bytes
 .../_static/images/compute-service-offerings.png   |  Bin 0 -> 75482 bytes
 source/_static/images/console-icon.png             |  Bin 0 -> 953 bytes
 source/_static/images/create-vpn-connection.png    |  Bin 0 -> 7703 bytes
 source/_static/images/dedicate-resource-button.png |  Bin 0 -> 7144 bytes
 source/_static/images/del-tier.png                 |  Bin 0 -> 815 bytes
 source/_static/images/delete-button.png            |  Bin 0 -> 735 bytes
 source/_static/images/destroy-instance.png         |  Bin 0 -> 815 bytes
 source/_static/images/detach-disk-icon.png         |  Bin 0 -> 953 bytes
 source/_static/images/dvswitch-config.png          |  Bin 0 -> 41955 bytes
 source/_static/images/dvswitchconfig.png           |  Bin 0 -> 38642 bytes
 source/_static/images/ec2-s3-configuration.png     |  Bin 0 -> 38778 bytes
 source/_static/images/edit-icon.png                |  Bin 0 -> 940 bytes
 source/_static/images/edit-traffic-type.png        |  Bin 0 -> 93662 bytes
 source/_static/images/egress-firewall-rule.png     |  Bin 0 -> 10413 bytes
 source/_static/images/eip-ns-basiczone.png         |  Bin 0 -> 63227 bytes
 source/_static/images/enable-disable-autoscale.png |  Bin 0 -> 913 bytes
 source/_static/images/enable-disable.png           |  Bin 0 -> 982 bytes
 source/_static/images/gslb.png                     |  Bin 0 -> 68556 bytes
 source/_static/images/guest-traffic-setup.png      |  Bin 0 -> 34022 bytes
 source/_static/images/http-access.png              |  Bin 0 -> 10214 bytes
 .../_static/images/hypervisorcomms-secstorage.png  |  Bin 0 -> 150919 bytes
 source/_static/images/hypervisorcomms.png          |  Bin 0 -> 78498 bytes
 source/_static/images/icon.svg                     |   37 +
 source/_static/images/infrastructure-overview.png  |  Bin 0 -> 11852 bytes
 source/_static/images/installation-complete.png    |  Bin 0 -> 20814 bytes
 source/_static/images/iso-icon.png                 |  Bin 0 -> 991 bytes
 source/_static/images/jp1.jpg                      |  Bin 0 -> 13705 bytes
 source/_static/images/jp2.jpg                      |  Bin 0 -> 14846 bytes
 .../_static/images/large-scale-redundant-setup.png |  Bin 0 -> 109117 bytes
 source/_static/images/ldap-config.png              |  Bin 0 -> 7872 bytes
 source/_static/images/mesos-integration-arch.jpg   |    0
 source/_static/images/metric-view.png              |  Bin 0 -> 246919 bytes
 source/_static/images/migrate-instance.png         |  Bin 0 -> 837 bytes
 source/_static/images/monkey.png                   |  Bin 0 -> 30274 bytes
 .../images/multi-node-management-server.png        |  Bin 0 -> 26912 bytes
 source/_static/images/multi-site-deployment.png    |  Bin 0 -> 68190 bytes
 source/_static/images/multi-tier-app.png           |  Bin 0 -> 200956 bytes
 source/_static/images/network-acl.png              |  Bin 0 -> 23333 bytes
 source/_static/images/network-setup-zone.png       |  Bin 0 -> 67410 bytes
 source/_static/images/network-singlepod.png        |  Bin 0 -> 18381 bytes
 source/_static/images/networking-egress-rule.png   |  Bin 0 -> 39649 bytes
 source/_static/images/networking-in-a-pod.png      |  Bin 0 -> 16365 bytes
 source/_static/images/networking-in-a-zone.png     |  Bin 0 -> 88746 bytes
 .../images/networking-infra-traffic-labels.png     |  Bin 0 -> 92572 bytes
 source/_static/images/networking-ingress-rule.png  |  Bin 0 -> 44719 bytes
 .../images/networking-zone-traffic-labels.png      |  Bin 0 -> 247970 bytes
 .../images/nic-bonding-and-multipath-io.png        |  Bin 0 -> 42030 bytes
 source/_static/images/nuage_iso_net_off.png        |  Bin 0 -> 300337 bytes
 source/_static/images/nuage_kvm_traffic_label.jpg  |  Bin 0 -> 82083 bytes
 source/_static/images/nuage_sha_net_off.png        |  Bin 0 -> 297457 bytes
 source/_static/images/nuage_source_nat_net_off.png |  Bin 0 -> 135190 bytes
 source/_static/images/nuage_underlay_api_usage.png |  Bin 0 -> 229780 bytes
 .../_static/images/nuage_vmware_traffic_label.jpg  |  Bin 0 -> 132936 bytes
 source/_static/images/nuage_vpc_net_off.png        |  Bin 0 -> 302542 bytes
 source/_static/images/nuage_vpc_off.png            |  Bin 0 -> 227849 bytes
 source/_static/images/nuage_vsd_device_add.png     |  Bin 0 -> 115589 bytes
 .../images/nuage_vsp_isolation_method_setting.png  |  Bin 0 -> 826955 bytes
 source/_static/images/nuage_vsp_nsp_enable.png     |  Bin 0 -> 287791 bytes
 source/_static/images/nuage_vsp_nsp_status.png     |  Bin 0 -> 512455 bytes
 source/_static/images/nuage_vsp_vpc_off.png        |  Bin 0 -> 221995 bytes
 source/_static/images/nvp-add-controller.png       |  Bin 0 -> 35928 bytes
 source/_static/images/nvp-enable-provider.png      |  Bin 0 -> 32158 bytes
 source/_static/images/nvp-network-offering.png     |  Bin 0 -> 104060 bytes
 source/_static/images/nvp-physical-network-stt.png |  Bin 0 -> 27317 bytes
 source/_static/images/nvp-vpc-offering-edit.png    |  Bin 0 -> 29279 bytes
 source/_static/images/ovs-network-offering.png     |  Bin 0 -> 113750 bytes
 .../images/ovs-physical-network-gre-enable.png     |  Bin 0 -> 41642 bytes
 source/_static/images/ovs-physical-network-gre.png |  Bin 0 -> 17354 bytes
 source/_static/images/packt.png                    |  Bin 0 -> 57435 bytes
 source/_static/images/parallel-mode.png            |  Bin 0 -> 11520 bytes
 source/_static/images/plugin1.jpg                  |  Bin 0 -> 32999 bytes
 source/_static/images/plugin2.jpg                  |  Bin 0 -> 35149 bytes
 source/_static/images/plugin3.jpg                  |  Bin 0 -> 41983 bytes
 source/_static/images/plugin4.jpg                  |  Bin 0 -> 32125 bytes
 source/_static/images/plugin_intro.jpg             |  Bin 0 -> 22247 bytes
 source/_static/images/pod-overview.png             |  Bin 0 -> 6036 bytes
 source/_static/images/provisioning-overview.png    |  Bin 0 -> 23622 bytes
 source/_static/images/region-overview.png          |  Bin 0 -> 22835 bytes
 source/_static/images/release-ip-icon.png          |  Bin 0 -> 815 bytes
 source/_static/images/remove-nic.png               |  Bin 0 -> 735 bytes
 source/_static/images/remove-tier.png              |  Bin 0 -> 7457 bytes
 source/_static/images/remove-vpc.png               |  Bin 0 -> 815 bytes
 source/_static/images/remove-vpn.png               |  Bin 0 -> 735 bytes
 source/_static/images/replace-acl-icon.png         |  Bin 0 -> 982 bytes
 source/_static/images/replace-acl-list.png         |  Bin 0 -> 7706 bytes
 source/_static/images/reset-vpn.png                |  Bin 0 -> 860 bytes
 source/_static/images/resize-volume-icon.png       |  Bin 0 -> 857 bytes
 source/_static/images/resize-volume.png            |  Bin 0 -> 11995 bytes
 source/_static/images/restart-vpc.png              |  Bin 0 -> 860 bytes
 source/_static/images/revert-vm.png                |  Bin 0 -> 860 bytes
 source/_static/images/s3-ss.png                    |  Bin 0 -> 24140 bytes
 source/_static/images/search-button.png            |  Bin 0 -> 1012 bytes
 source/_static/images/select-vm-staticnat-vpc.png  |  Bin 0 -> 17472 bytes
 source/_static/images/separate-storage-network.png |  Bin 0 -> 44556 bytes
 source/_static/images/set-default-nic.png          |  Bin 0 -> 1012 bytes
 source/_static/images/small-scale-deployment.png   |  Bin 0 -> 50772 bytes
 source/_static/images/software-license.png         |  Bin 0 -> 124257 bytes
 source/_static/images/stop-instance-icon.png       |  Bin 0 -> 955 bytes
 source/_static/images/subnetting_storage.png       |  Bin 0 -> 120501 bytes
 source/_static/images/suspend-icon.png             |  Bin 0 -> 982 bytes
 source/_static/images/sysmanager.png               |  Bin 0 -> 114821 bytes
 source/_static/images/traffic-type.png             |  Bin 0 -> 19159 bytes
 source/_static/images/update-ssl-icon.png          |  Bin 0 -> 8812 bytes
 source/_static/images/update-ssl.png               |  Bin 0 -> 30619 bytes
 source/_static/images/vds-name.png                 |  Bin 0 -> 64739 bytes
 source/_static/images/view-console-button.png      |  Bin 0 -> 59996 bytes
 source/_static/images/view-systemvm-details.png    |  Bin 0 -> 25483 bytes
 source/_static/images/vm-lifecycle.png             |  Bin 0 -> 20783 bytes
 source/_static/images/vmware-increase-ports.png    |  Bin 0 -> 66143 bytes
 source/_static/images/vmware-iscsi-datastore.png   |  Bin 0 -> 54352 bytes
 source/_static/images/vmware-iscsi-general.png     |  Bin 0 -> 15723 bytes
 .../images/vmware-iscsi-initiator-properties.png   |  Bin 0 -> 45592 bytes
 source/_static/images/vmware-iscsi-initiator.png   |  Bin 0 -> 105201 bytes
 source/_static/images/vmware-iscsi-target-add.png  |  Bin 0 -> 18509 bytes
 .../images/vmware-mgt-network-properties.png       |  Bin 0 -> 42767 bytes
 source/_static/images/vmware-nexus-add-cluster.png |  Bin 0 -> 37083 bytes
 .../_static/images/vmware-nexus-port-profile.png   |  Bin 0 -> 118083 bytes
 source/_static/images/vmware-physical-network.png  |  Bin 0 -> 136848 bytes
 .../_static/images/vmware-vswitch-properties.png   |  Bin 0 -> 32376 bytes
 source/_static/images/vpc-lb.png                   |  Bin 0 -> 181811 bytes
 source/_static/images/vpc-setting.png              |  Bin 0 -> 5636 bytes
 source/_static/images/vpn-icon.png                 |  Bin 0 -> 1012 bytes
 source/_static/images/vpn/osxvpn_connected.png     |  Bin 0 -> 102118 bytes
 source/_static/images/vpn/osxvpn_form1.png         |  Bin 0 -> 106299 bytes
 source/_static/images/vpn/osxvpn_form2.png         |  Bin 0 -> 93670 bytes
 source/_static/images/vpn/osxvpn_form3.png         |  Bin 0 -> 121544 bytes
 source/_static/images/vpn/osxvpn_netconf.png       |  Bin 0 -> 98098 bytes
 source/_static/images/vpn/win1.png                 |  Bin 0 -> 97933 bytes
 source/_static/images/vpn/win10.png                |  Bin 0 -> 103531 bytes
 source/_static/images/vpn/win11.png                |  Bin 0 -> 57332 bytes
 source/_static/images/vpn/win12.png                |  Bin 0 -> 130877 bytes
 source/_static/images/vpn/win13.png                |  Bin 0 -> 131804 bytes
 source/_static/images/vpn/win14.png                |  Bin 0 -> 132416 bytes
 source/_static/images/vpn/win2.png                 |  Bin 0 -> 53656 bytes
 source/_static/images/vpn/win3.png                 |  Bin 0 -> 49302 bytes
 source/_static/images/vpn/win4.png                 |  Bin 0 -> 51313 bytes
 source/_static/images/vpn/win5.png                 |  Bin 0 -> 73394 bytes
 source/_static/images/vpn/win6.png                 |  Bin 0 -> 48772 bytes
 source/_static/images/vpn/win7.png                 |  Bin 0 -> 51047 bytes
 source/_static/images/vpn/win8.png                 |  Bin 0 -> 39525 bytes
 source/_static/images/vpn/win9.png                 |  Bin 0 -> 51403 bytes
 source/_static/images/vr-upgrade.png               |  Bin 0 -> 940 bytes
 source/_static/images/vsphere-client.png           |  Bin 0 -> 81246 bytes
 source/_static/images/vxlan-physicalnetwork.png    |  Bin 0 -> 68376 bytes
 source/_static/images/vxlan-trafficlabel.png       |  Bin 0 -> 61473 bytes
 source/_static/images/vxlan-vniconfig.png          |  Bin 0 -> 18161 bytes
 source/_static/images/workloads.png                |  Bin 0 -> 69265 bytes
 source/_static/images/zone-overview.png            |  Bin 0 -> 11852 bytes
 source/_static/theme_overrides.css                 |   18 +
 source/adminguide/accounts.rst                     |  437 +
 source/adminguide/administration.rst               |   77 +
 source/adminguide/api.rst                          |   90 +
 source/adminguide/autoscale_without_netscaler.rst  |  177 +
 source/adminguide/events.rst                       |  368 +
 source/adminguide/hosts.rst                        |  747 ++
 source/adminguide/index.rst                        |  173 +
 source/adminguide/locale/pot/accounts.pot          |  409 +
 source/adminguide/locale/pot/administration.pot    |   63 +
 source/adminguide/locale/pot/api.pot               |  123 +
 source/adminguide/locale/pot/events.pot            |  332 +
 source/adminguide/locale/pot/hosts.pot             |  828 ++
 source/adminguide/locale/pot/index.pot             |  128 +
 source/adminguide/locale/pot/management.pot        |  458 +
 source/adminguide/locale/pot/networking.pot        |  765 ++
 .../pot/networking/acquiring_an_ip_address.pot     |   73 +
 .../locale/pot/networking/advanced_zone_config.pot |  252 +
 .../locale/pot/networking/basic_zone_config.pot    |   28 +
 .../locale/pot/networking/dns_and_dhcp.pot         |   28 +
 .../locale/pot/networking/elastic_ips.pot          |   98 +
 .../external_firewalls_and_load_balancers.pot      |  703 ++
 .../networking/global_server_load_balancing.pot    |  573 ++
 .../locale/pot/networking/guest_ip_ranges.pot      |   33 +
 .../locale/pot/networking/guest_traffic.pot        |   53 +
 .../locale/pot/networking/inter_vlan_routing.pot   |  118 +
 .../networking/ip_forwarding_and_firewalling.pot   |  393 +
 .../locale/pot/networking/ip_load_balancing.pot    |   48 +
 .../ip_reservation_in_guest_networks.pot           |  238 +
 .../isolation_in_advanced_zone_with_vlan.pot       |  273 +
 .../pot/networking/multiple_guest_networks.pot     |  312 +
 .../locale/pot/networking/multiple_ip_ranges.pot   |   48 +
 .../pot/networking/multiple_ips_on_single_nic.pot  |  128 +
 .../multiple_subnets_in_shared_network.pot         |  158 +
 .../locale/pot/networking/networking_in_pod.pot    |   58 +
 .../locale/pot/networking/networking_in_zone.pot   |   43 +
 .../locale/pot/networking/palo_alto_config.pot     |  781 ++
 .../locale/pot/networking/persistent_networks.pot  |  123 +
 .../locale/pot/networking/portable_ips.pot         |  210 +
 .../public_ips_and_vlans_for_accounts.pot          |  261 +
 .../pot/networking/releasing_an_ip_address.pot     |   58 +
 .../locale/pot/networking/remote_access_vpn.pot    |  997 ++
 .../locale/pot/networking/security_groups.pot      |  265 +
 .../locale/pot/networking/static_nat.pot           |   83 +
 .../networking/virtual_private_cloud_config.pot    | 2019 +++++
 source/adminguide/locale/pot/networking2.pot       | 6796 ++++++++++++++
 .../locale/pot/networking_and_traffic.pot          | 7535 +++++++++++++++
 source/adminguide/locale/pot/projects.pot          |  600 ++
 source/adminguide/locale/pot/reliability.pot       |  368 +
 source/adminguide/locale/pot/service_offerings.pot |  809 ++
 source/adminguide/locale/pot/storage.pot           | 1106 +++
 source/adminguide/locale/pot/systemvm.pot          |  740 ++
 source/adminguide/locale/pot/templates.pot         | 1215 +++
 source/adminguide/locale/pot/troubleshooting.pot   |  383 +
 source/adminguide/locale/pot/tuning.pot            |  123 +
 source/adminguide/locale/pot/ui.pot                |  190 +
 source/adminguide/locale/pot/usage.pot             | 1497 +++
 source/adminguide/locale/pot/virtual_machines.pot  | 1611 ++++
 .../locale/zh_CN/LC_MESSAGES/accounts.mo           |  Bin 0 -> 21352 bytes
 .../locale/zh_CN/LC_MESSAGES/accounts.po           |  550 ++
 .../locale/zh_CN/LC_MESSAGES/administration.mo     |  Bin 0 -> 4577 bytes
 .../locale/zh_CN/LC_MESSAGES/administration.po     |   95 +
 source/adminguide/locale/zh_CN/LC_MESSAGES/api.mo  |  Bin 0 -> 5123 bytes
 source/adminguide/locale/zh_CN/LC_MESSAGES/api.po  |  154 +
 .../adminguide/locale/zh_CN/LC_MESSAGES/events.mo  |  Bin 0 -> 14126 bytes
 .../adminguide/locale/zh_CN/LC_MESSAGES/events.po  |  411 +
 .../adminguide/locale/zh_CN/LC_MESSAGES/hosts.mo   |  Bin 0 -> 37103 bytes
 .../adminguide/locale/zh_CN/LC_MESSAGES/hosts.po   | 1058 +++
 .../adminguide/locale/zh_CN/LC_MESSAGES/index.mo   |  Bin 0 -> 1759 bytes
 .../adminguide/locale/zh_CN/LC_MESSAGES/index.po   |  138 +
 .../locale/zh_CN/LC_MESSAGES/management.mo         |  Bin 0 -> 21210 bytes
 .../locale/zh_CN/LC_MESSAGES/management.po         |  602 ++
 .../locale/zh_CN/LC_MESSAGES/networking.mo         |  Bin 0 -> 28692 bytes
 .../locale/zh_CN/LC_MESSAGES/networking.po         |  900 ++
 .../networking/acquiring_an_ip_address.mo          |  Bin 0 -> 1948 bytes
 .../networking/acquiring_an_ip_address.po          |   80 +
 .../LC_MESSAGES/networking/advanced_zone_config.mo |  Bin 0 -> 7448 bytes
 .../LC_MESSAGES/networking/advanced_zone_config.po |  290 +
 .../LC_MESSAGES/networking/basic_zone_config.mo    |  Bin 0 -> 1194 bytes
 .../LC_MESSAGES/networking/basic_zone_config.po    |   32 +
 .../zh_CN/LC_MESSAGES/networking/dns_and_dhcp.mo   |  Bin 0 -> 830 bytes
 .../zh_CN/LC_MESSAGES/networking/dns_and_dhcp.po   |   30 +
 .../zh_CN/LC_MESSAGES/networking/elastic_ips.mo    |  Bin 0 -> 8306 bytes
 .../zh_CN/LC_MESSAGES/networking/elastic_ips.po    |  157 +
 .../external_firewalls_and_load_balancers.mo       |  Bin 0 -> 45696 bytes
 .../external_firewalls_and_load_balancers.po       | 1056 +++
 .../networking/global_server_load_balancing.mo     |  Bin 0 -> 32483 bytes
 .../networking/global_server_load_balancing.po     |  789 ++
 .../LC_MESSAGES/networking/guest_ip_ranges.mo      |  Bin 0 -> 1566 bytes
 .../LC_MESSAGES/networking/guest_ip_ranges.po      |   41 +
 .../zh_CN/LC_MESSAGES/networking/guest_traffic.mo  |  Bin 0 -> 3155 bytes
 .../zh_CN/LC_MESSAGES/networking/guest_traffic.po  |   71 +
 .../LC_MESSAGES/networking/inter_vlan_routing.mo   |  Bin 0 -> 6689 bytes
 .../LC_MESSAGES/networking/inter_vlan_routing.po   |  167 +
 .../networking/ip_forwarding_and_firewalling.mo    |  Bin 0 -> 16250 bytes
 .../networking/ip_forwarding_and_firewalling.po    |  499 +
 .../LC_MESSAGES/networking/ip_load_balancing.mo    |  Bin 0 -> 1143 bytes
 .../LC_MESSAGES/networking/ip_load_balancing.po    |   52 +
 .../networking/ip_reservation_in_guest_networks.mo |  Bin 0 -> 7425 bytes
 .../networking/ip_reservation_in_guest_networks.po |  282 +
 .../isolation_in_advanced_zone_with_vlan.mo        |  Bin 0 -> 14175 bytes
 .../isolation_in_advanced_zone_with_vlan.po        |  363 +
 .../networking/multiple_guest_networks.mo          |  Bin 0 -> 9228 bytes
 .../networking/multiple_guest_networks.po          |  362 +
 .../LC_MESSAGES/networking/multiple_ip_ranges.mo   |  Bin 0 -> 2996 bytes
 .../LC_MESSAGES/networking/multiple_ip_ranges.po   |   65 +
 .../networking/multiple_ips_on_single_nic.mo       |  Bin 0 -> 6064 bytes
 .../networking/multiple_ips_on_single_nic.po       |  165 +
 .../multiple_subnets_in_shared_network.mo          |  Bin 0 -> 4972 bytes
 .../multiple_subnets_in_shared_network.po          |  180 +
 .../LC_MESSAGES/networking/networking_in_pod.mo    |  Bin 0 -> 2073 bytes
 .../LC_MESSAGES/networking/networking_in_pod.po    |   70 +
 .../LC_MESSAGES/networking/networking_in_zone.mo   |  Bin 0 -> 1478 bytes
 .../LC_MESSAGES/networking/networking_in_zone.po   |   50 +
 .../LC_MESSAGES/networking/palo_alto_config.mo     |  Bin 0 -> 552 bytes
 .../LC_MESSAGES/networking/palo_alto_config.po     |  932 ++
 .../LC_MESSAGES/networking/persistent_networks.mo  |  Bin 0 -> 6221 bytes
 .../LC_MESSAGES/networking/persistent_networks.po  |  163 +
 .../zh_CN/LC_MESSAGES/networking/portable_ips.mo   |  Bin 0 -> 5993 bytes
 .../zh_CN/LC_MESSAGES/networking/portable_ips.po   |  233 +
 .../public_ips_and_vlans_for_accounts.mo           |  Bin 0 -> 6136 bytes
 .../public_ips_and_vlans_for_accounts.po           |  286 +
 .../networking/releasing_an_ip_address.mo          |  Bin 0 -> 1546 bytes
 .../networking/releasing_an_ip_address.po          |   61 +
 .../LC_MESSAGES/networking/remote_access_vpn.mo    |  Bin 0 -> 34200 bytes
 .../LC_MESSAGES/networking/remote_access_vpn.po    | 1199 +++
 .../LC_MESSAGES/networking/security_groups.mo      |  Bin 0 -> 14395 bytes
 .../LC_MESSAGES/networking/security_groups.po      |  366 +
 .../zh_CN/LC_MESSAGES/networking/static_nat.mo     |  Bin 0 -> 2133 bytes
 .../zh_CN/LC_MESSAGES/networking/static_nat.po     |   95 +
 .../networking/virtual_private_cloud_config.mo     |  Bin 0 -> 62734 bytes
 .../networking/virtual_private_cloud_config.po     | 2403 +++++
 .../locale/zh_CN/LC_MESSAGES/networking2.mo        |  Bin 0 -> 286127 bytes
 .../locale/zh_CN/LC_MESSAGES/networking2.po        | 8448 +++++++++++++++++
 .../zh_CN/LC_MESSAGES/networking_and_traffic.mo    |  Bin 0 -> 280835 bytes
 .../zh_CN/LC_MESSAGES/networking_and_traffic.po    | 9580 ++++++++++++++++++++
 .../locale/zh_CN/LC_MESSAGES/projects.mo           |  Bin 0 -> 26445 bytes
 .../locale/zh_CN/LC_MESSAGES/projects.po           |  755 ++
 .../locale/zh_CN/LC_MESSAGES/reliability.mo        |  Bin 0 -> 17946 bytes
 .../locale/zh_CN/LC_MESSAGES/reliability.po        |  485 +
 .../locale/zh_CN/LC_MESSAGES/service_offerings.mo  |  Bin 0 -> 40910 bytes
 .../locale/zh_CN/LC_MESSAGES/service_offerings.po  | 1079 +++
 .../adminguide/locale/zh_CN/LC_MESSAGES/storage.mo |  Bin 0 -> 54475 bytes
 .../adminguide/locale/zh_CN/LC_MESSAGES/storage.po | 1460 +++
 .../locale/zh_CN/LC_MESSAGES/systemvm.mo           |  Bin 0 -> 31167 bytes
 .../locale/zh_CN/LC_MESSAGES/systemvm.po           |  955 ++
 .../locale/zh_CN/LC_MESSAGES/templates.mo          |  Bin 0 -> 53455 bytes
 .../locale/zh_CN/LC_MESSAGES/templates.po          | 1554 ++++
 .../locale/zh_CN/LC_MESSAGES/troubleshooting.mo    |  Bin 0 -> 17260 bytes
 .../locale/zh_CN/LC_MESSAGES/troubleshooting.po    |  497 +
 .../adminguide/locale/zh_CN/LC_MESSAGES/tuning.mo  |  Bin 0 -> 6802 bytes
 .../adminguide/locale/zh_CN/LC_MESSAGES/tuning.po  |  165 +
 source/adminguide/locale/zh_CN/LC_MESSAGES/ui.mo   |  Bin 0 -> 11120 bytes
 source/adminguide/locale/zh_CN/LC_MESSAGES/ui.po   |  265 +
 .../adminguide/locale/zh_CN/LC_MESSAGES/usage.mo   |  Bin 0 -> 42801 bytes
 .../adminguide/locale/zh_CN/LC_MESSAGES/usage.po   | 1655 ++++
 .../locale/zh_CN/LC_MESSAGES/virtual_machines.mo   |  Bin 0 -> 70728 bytes
 .../locale/zh_CN/LC_MESSAGES/virtual_machines.po   | 2048 +++++
 source/adminguide/management.rst                   |  512 ++
 source/adminguide/networking.rst                   |  408 +
 .../networking/acquiring_an_ip_address.rst         |   42 +
 .../adminguide/networking/advanced_zone_config.rst |  152 +
 source/adminguide/networking/basic_zone_config.rst |   24 +
 source/adminguide/networking/dns_and_dhcp.rst      |   22 +
 source/adminguide/networking/elastic_ips.rst       |  104 +
 .../external_firewalls_and_load_balancers.rst      |  661 ++
 .../networking/global_server_load_balancing.rst    |  453 +
 source/adminguide/networking/guest_ip_ranges.rst   |   29 +
 source/adminguide/networking/guest_traffic.rst     |   50 +
 .../adminguide/networking/inter_vlan_routing.rst   |   96 +
 .../networking/ip_forwarding_and_firewalling.rst   |  280 +
 source/adminguide/networking/ip_load_balancing.rst |   31 +
 .../ip_reservation_in_guest_networks.rst           |  127 +
 .../isolation_in_advanced_zone_with_vlan.rst       |  202 +
 .../networking/multiple_guest_networks.rst         |  207 +
 .../adminguide/networking/multiple_ip_ranges.rst   |   43 +
 .../networking/multiple_ips_on_single_nic.rst      |   98 +
 .../multiple_subnets_in_shared_network.rst         |   99 +
 source/adminguide/networking/networking_in_pod.rst |   45 +
 .../adminguide/networking/networking_in_zone.rst   |   34 +
 source/adminguide/networking/palo_alto_config.rst  |  475 +
 .../adminguide/networking/persistent_networks.rst  |   94 +
 source/adminguide/networking/portable_ips.rst      |  131 +
 .../public_ips_and_vlans_for_accounts.rst          |  154 +
 .../networking/releasing_an_ip_address.rst         |   38 +
 source/adminguide/networking/remote_access_vpn.rst |  157 +
 source/adminguide/networking/security_groups.rst   |  215 +
 source/adminguide/networking/site_to_site_vpn.rst  |  451 +
 source/adminguide/networking/static_nat.rst        |   56 +
 .../adminguide/networking/using_remote_access.rst  |  148 +
 .../networking/virtual_private_cloud_config.rst    | 1442 +++
 source/adminguide/networking_and_traffic.rst       |   81 +
 source/adminguide/projects.rst                     |  428 +
 source/adminguide/reliability.rst                  |  261 +
 source/adminguide/service_offerings.rst            |  647 ++
 source/adminguide/storage.rst                      |  804 ++
 source/adminguide/systemvm.rst                     |  554 ++
 source/adminguide/templates.rst                    |  313 +
 source/adminguide/templates/_convert_hyperv.rst    |   88 +
 source/adminguide/templates/_create_linux.rst      |  261 +
 source/adminguide/templates/_create_windows.rst    |  220 +
 source/adminguide/templates/_import_ami.rst        |  192 +
 source/adminguide/templates/_password.rst          |   85 +
 source/adminguide/troubleshooting.rst              |  456 +
 source/adminguide/tuning.rst                       |  125 +
 source/adminguide/ui.rst                           |  173 +
 source/adminguide/usage.rst                        |  929 ++
 source/adminguide/virtual_machines.rst             | 1356 +++
 source/adminguide/virtual_machines/user-data.rst   |  119 +
 .../choosing_deployment_architecture.rst           |  367 +
 source/conceptsandterminology/concepts.rst         |  723 ++
 source/conceptsandterminology/index.rst            |   64 +
 .../locale/pot/administration_guide.pot            | 1011 +++
 source/conceptsandterminology/locale/pot/alloc.pot |  409 +
 .../conceptsandterminology/locale/pot/ansible.pot  |  383 +
 .../conceptsandterminology/locale/pot/concepts.pot | 1181 +++
 source/conceptsandterminology/locale/pot/dev.pot   | 2817 ++++++
 .../locale/pot/developer_guide.pot                 |  528 ++
 source/conceptsandterminology/locale/pot/index.pot |   78 +
 .../locale/pot/networking.pot                      | 1940 ++++
 .../conceptsandterminology/locale/pot/plugins.pot  |  783 ++
 source/conceptsandterminology/network_setup.rst    | 1048 +++
 source/conceptsandterminology/storage_setup.rst    |  361 +
 source/conf.py                                     |  195 +
 source/developersguide/alloc.rst                   |  315 +
 source/developersguide/ansible.rst                 |  441 +
 source/developersguide/dev.rst                     | 1340 +++
 source/developersguide/developer_guide.rst         |  703 ++
 source/developersguide/get_help.rst                |   78 +
 source/developersguide/index.rst                   |   38 +
 source/developersguide/plugins.rst                 |  723 ++
 source/index.rst                                   |   68 +
 source/installguide/building_from_source.rst       |  511 ++
 source/installguide/configuration.rst              | 1633 ++++
 source/installguide/encryption.rst                 |  132 +
 source/installguide/hypervisor/hyperv.rst          |  268 +
 source/installguide/hypervisor/kvm.rst             | 1112 +++
 source/installguide/hypervisor/lxc.rst             |  670 ++
 source/installguide/hypervisor/vsphere.rst         | 1028 +++
 source/installguide/hypervisor/xenserver.rst       |  816 ++
 source/installguide/index.rst                      |   79 +
 .../locale/pot/building_from_source.pot            |  433 +
 .../pot/choosing_deployment_architecture.pot       |  511 ++
 source/installguide/locale/pot/configuration.pot   | 2550 ++++++
 .../installguide/locale/pot/hypervisor/hyperv.pot  |  449 +
 source/installguide/locale/pot/hypervisor/kvm.pot  |  949 ++
 source/installguide/locale/pot/hypervisor/lxc.pot  |  621 ++
 .../installguide/locale/pot/hypervisor/vsphere.pot | 1681 ++++
 .../locale/pot/hypervisor/xenserver.pot            |  944 ++
 .../locale/pot/hypervisor_installation.pot         | 4221 +++++++++
 source/installguide/locale/pot/index.pot           |   98 +
 source/installguide/locale/pot/installation.pot    | 1224 +++
 .../installguide/locale/pot/managing_networks.pot  | 6769 ++++++++++++++
 source/installguide/locale/pot/network_setup.pot   | 1703 ++++
 .../locale/pot/optional_installation.pot           | 1252 +++
 source/installguide/locale/pot/qig.pot             |  682 ++
 source/installguide/locale/pot/storage_setup.pot   |  290 +
 .../zh_CN/LC_MESSAGES/building_from_source.mo      |  Bin 0 -> 20777 bytes
 .../zh_CN/LC_MESSAGES/building_from_source.po      |  582 ++
 .../choosing_deployment_architecture.mo            |  Bin 0 -> 20675 bytes
 .../choosing_deployment_architecture.po            |  648 ++
 .../locale/zh_CN/LC_MESSAGES/configuration.mo      |  Bin 0 -> 108662 bytes
 .../locale/zh_CN/LC_MESSAGES/configuration.po      | 3249 +++++++
 .../locale/zh_CN/LC_MESSAGES/hypervisor/hyperv.mo  |  Bin 0 -> 12390 bytes
 .../locale/zh_CN/LC_MESSAGES/hypervisor/hyperv.po  |  538 ++
 .../locale/zh_CN/LC_MESSAGES/hypervisor/kvm.mo     |  Bin 0 -> 27536 bytes
 .../locale/zh_CN/LC_MESSAGES/hypervisor/kvm.po     | 1095 +++
 .../locale/zh_CN/LC_MESSAGES/hypervisor/lxc.mo     |  Bin 0 -> 18006 bytes
 .../locale/zh_CN/LC_MESSAGES/hypervisor/lxc.po     |  726 ++
 .../locale/zh_CN/LC_MESSAGES/hypervisor/vsphere.mo |  Bin 0 -> 64069 bytes
 .../locale/zh_CN/LC_MESSAGES/hypervisor/vsphere.po | 2089 +++++
 .../zh_CN/LC_MESSAGES/hypervisor/xenserver.mo      |  Bin 0 -> 41623 bytes
 .../zh_CN/LC_MESSAGES/hypervisor/xenserver.po      | 1237 +++
 .../zh_CN/LC_MESSAGES/hypervisor_installation.mo   |  Bin 0 -> 150499 bytes
 .../zh_CN/LC_MESSAGES/hypervisor_installation.po   | 5173 +++++++++++
 .../installguide/locale/zh_CN/LC_MESSAGES/index.mo |  Bin 0 -> 1527 bytes
 .../installguide/locale/zh_CN/LC_MESSAGES/index.po |  115 +
 .../locale/zh_CN/LC_MESSAGES/installation.mo       |  Bin 0 -> 52835 bytes
 .../locale/zh_CN/LC_MESSAGES/installation.po       | 1592 ++++
 .../locale/zh_CN/LC_MESSAGES/managing_networks.mo  |  Bin 0 -> 292007 bytes
 .../locale/zh_CN/LC_MESSAGES/managing_networks.po  | 8467 +++++++++++++++++
 .../locale/zh_CN/LC_MESSAGES/network_setup.mo      |  Bin 0 -> 58589 bytes
 .../locale/zh_CN/LC_MESSAGES/network_setup.po      | 2041 +++++
 .../zh_CN/LC_MESSAGES/optional_installation.mo     |  Bin 0 -> 31829 bytes
 .../zh_CN/LC_MESSAGES/optional_installation.po     | 1404 +++
 .../installguide/locale/zh_CN/LC_MESSAGES/qig.mo   |  Bin 0 -> 26949 bytes
 .../installguide/locale/zh_CN/LC_MESSAGES/qig.po   |  872 ++
 .../locale/zh_CN/LC_MESSAGES/storage_setup.mo      |  Bin 0 -> 9018 bytes
 .../locale/zh_CN/LC_MESSAGES/storage_setup.po      |  341 +
 .../installguide/management-server/_database.rst   |  377 +
 source/installguide/management-server/_nfs.rst     |  248 +
 .../management-server/_pkg_install.rst             |   49 +
 .../installguide/management-server/_pkg_repo.rst   |   93 +
 .../management-server/_prerequisite.rst            |   94 +
 .../installguide/management-server/_second_mgt.rst |   70 +
 .../installguide/management-server/_systemvm.rst   |  120 +
 .../installguide/management-server/_vhd-util.rst   |   26 +
 source/installguide/management-server/index.rst    |   56 +
 source/installguide/optional_installation.rst      |  804 ++
 source/installguide/overview/_overview.rst         |   67 +
 source/installguide/overview/_requirements.rst     |   83 +
 source/installguide/overview/index.rst             |   46 +
 source/plugins/cloudian-connector.rst              |  473 +
 source/plugins/index.rst                           |   40 +
 source/plugins/ipv6.rst                            |  199 +
 source/plugins/midonet.rst                         |  168 +
 source/plugins/nicira-plugin.rst                   |  402 +
 source/plugins/nuage-plugin.rst                    |  513 ++
 source/plugins/ovs-plugin.rst                      |  274 +
 source/plugins/quota.rst                           |  189 +
 source/plugins/vxlan.rst                           |  428 +
 source/quickinstallationguide/qig.rst              |  695 ++
 source/releasenotes/about.rst                      |   84 +
 source/releasenotes/api-changes.rst                | 1009 +++
 source/releasenotes/compat.rst                     |  113 +
 source/releasenotes/fixed_issues.rst               | 1700 ++++
 source/releasenotes/index.rst                      |   65 +
 source/releasenotes/known_issues.rst               |  363 +
 source/releasenotes/locale/ja/LC_MESSAGES/about.mo |  Bin 0 -> 499 bytes
 source/releasenotes/locale/ja/LC_MESSAGES/about.po | 5927 ++++++++++++
 .../locale/ja/LC_MESSAGES/api-changes.mo           |  Bin 0 -> 499 bytes
 .../locale/ja/LC_MESSAGES/api-changes.po           |  270 +
 .../releasenotes/locale/ja/LC_MESSAGES/compat.mo   |  Bin 0 -> 499 bytes
 .../releasenotes/locale/ja/LC_MESSAGES/compat.po   |  192 +
 source/releasenotes/locale/ja/LC_MESSAGES/index.mo |  Bin 0 -> 2801 bytes
 source/releasenotes/locale/ja/LC_MESSAGES/index.po |   52 +
 .../releasenotes/locale/ja/LC_MESSAGES/rnotes.mo   |  Bin 0 -> 499 bytes
 .../releasenotes/locale/ja/LC_MESSAGES/rnotes.po   | 2600 ++++++
 .../locale/pot/.doctrees/about.doctree             |  Bin 0 -> 722802 bytes
 .../locale/pot/.doctrees/api-changes.doctree       |  Bin 0 -> 26913 bytes
 .../locale/pot/.doctrees/compat.doctree            |  Bin 0 -> 16100 bytes
 .../locale/pot/.doctrees/environment.pickle        |  Bin 0 -> 22389 bytes
 .../locale/pot/.doctrees/index.doctree             |  Bin 0 -> 9155 bytes
 .../locale/pot/.doctrees/rnotes.doctree            |  Bin 0 -> 620901 bytes
 source/releasenotes/locale/pot/about.pot           | 4903 ++++++++++
 source/releasenotes/locale/pot/api-changes.pot     |  264 +
 source/releasenotes/locale/pot/compat.pot          |  178 +
 source/releasenotes/locale/pot/index.pot           |   38 +
 source/releasenotes/locale/pot/rnotes.pot          | 2328 +++++
 source/upgrading/index.rst                         |   54 +
 source/upgrading/locale/ja/LC_MESSAGES/about.mo    |  Bin 0 -> 499 bytes
 source/upgrading/locale/ja/LC_MESSAGES/about.po    | 5927 ++++++++++++
 .../upgrading/locale/ja/LC_MESSAGES/api-changes.mo |  Bin 0 -> 499 bytes
 .../upgrading/locale/ja/LC_MESSAGES/api-changes.po |  270 +
 source/upgrading/locale/ja/LC_MESSAGES/compat.mo   |  Bin 0 -> 499 bytes
 source/upgrading/locale/ja/LC_MESSAGES/compat.po   |  192 +
 source/upgrading/locale/ja/LC_MESSAGES/index.mo    |  Bin 0 -> 2801 bytes
 source/upgrading/locale/ja/LC_MESSAGES/index.po    |   52 +
 source/upgrading/locale/ja/LC_MESSAGES/rnotes.mo   |  Bin 0 -> 499 bytes
 source/upgrading/locale/ja/LC_MESSAGES/rnotes.po   | 2600 ++++++
 .../upgrading/locale/pot/.doctrees/about.doctree   |  Bin 0 -> 722802 bytes
 .../locale/pot/.doctrees/api-changes.doctree       |  Bin 0 -> 26913 bytes
 .../upgrading/locale/pot/.doctrees/compat.doctree  |  Bin 0 -> 16100 bytes
 .../locale/pot/.doctrees/environment.pickle        |  Bin 0 -> 22389 bytes
 .../upgrading/locale/pot/.doctrees/index.doctree   |  Bin 0 -> 9155 bytes
 .../upgrading/locale/pot/.doctrees/rnotes.doctree  |  Bin 0 -> 620901 bytes
 source/upgrading/locale/pot/about.pot              | 4903 ++++++++++
 source/upgrading/locale/pot/api-changes.pot        |  264 +
 source/upgrading/locale/pot/compat.pot             |  178 +
 source/upgrading/locale/pot/index.pot              |   38 +
 source/upgrading/locale/pot/rnotes.pot             | 2328 +++++
 source/upgrading/upgrade/_java_8_ubuntu.rst        |   31 +
 source/upgrading/upgrade/_mysql_connector.rst      |   33 +
 source/upgrading/upgrade/_no-sysvm_templates.rst   |   21 +
 source/upgrading/upgrade/_sysvm_manual_hotfix.rst  |  115 +
 source/upgrading/upgrade/_sysvm_restart.rst        |   52 +
 source/upgrading/upgrade/_sysvm_templates.rst      |  145 +
 .../upgrading/upgrade/_sysvm_templates_pre45.rst   |  219 +
 source/upgrading/upgrade/_upgrade_header.rst       |   37 +
 source/upgrading/upgrade/_xenserver_upg.rst        |   57 +
 source/upgrading/upgrade/upgrade-4.10.rst          |  421 +
 source/upgrading/upgrade/upgrade-4.11.rst          |  416 +
 source/upgrading/upgrade/upgrade-4.2.rst           |  441 +
 source/upgrading/upgrade/upgrade-4.3.rst           |  430 +
 source/upgrading/upgrade/upgrade-4.4.rst           |  443 +
 source/upgrading/upgrade/upgrade-4.5.rst           |  434 +
 source/upgrading/upgrade/upgrade-4.6.rst           |  424 +
 source/upgrading/upgrade/upgrade-4.7.rst           |  417 +
 source/upgrading/upgrade/upgrade-4.8.rst           |  421 +
 source/upgrading/upgrade/upgrade-4.9.rst           |  420 +
 source/upgrading/upgrade/upgrade_notes.rst         |  106 +
 source/upgrading/upgrade/valid_source.rst          |  103 +
 572 files changed, 218306 insertions(+)

diff --git a/Makefile b/Makefile
new file mode 100644
index 0000000..011b858
--- /dev/null
+++ b/Makefile
@@ -0,0 +1,20 @@
+# Minimal makefile for Sphinx documentation
+#
+
+# You can set these variables from the command line.
+SPHINXOPTS    =
+SPHINXBUILD   = sphinx-build
+SPHINXPROJ    = ApacheCloudStack
+SOURCEDIR     = source
+BUILDDIR      = build
+
+# Put it first so that "make" without argument is like "make help".
+help:
+	@$(SPHINXBUILD) -M help "$(SOURCEDIR)" "$(BUILDDIR)" $(SPHINXOPTS) $(O)
+
+.PHONY: help Makefile
+
+# Catch-all target: route all unknown targets to Sphinx using the new
+# "make mode" option.  $(O) is meant as a shortcut for $(SPHINXOPTS).
+%: Makefile
+	@$(SPHINXBUILD) -M $@ "$(SOURCEDIR)" "$(BUILDDIR)" $(SPHINXOPTS) $(O)
\ No newline at end of file
diff --git a/make.bat b/make.bat
new file mode 100644
index 0000000..d704d3c
--- /dev/null
+++ b/make.bat
@@ -0,0 +1,36 @@
+@ECHO OFF
+
+pushd %~dp0
+
+REM Command file for Sphinx documentation
+
+if "%SPHINXBUILD%" == "" (
+	set SPHINXBUILD=sphinx-build
+)
+set SOURCEDIR=source
+set BUILDDIR=build
+set SPHINXPROJ=ApacheCloudStack
+
+if "%1" == "" goto help
+
+%SPHINXBUILD% >NUL 2>NUL
+if errorlevel 9009 (
+	echo.
+	echo.The 'sphinx-build' command was not found. Make sure you have Sphinx
+	echo.installed, then set the SPHINXBUILD environment variable to point
+	echo.to the full path of the 'sphinx-build' executable. Alternatively you
+	echo.may add the Sphinx directory to PATH.
+	echo.
+	echo.If you don't have Sphinx installed, grab it from
+	echo.http://sphinx-doc.org/
+	exit /b 1
+)
+rd %BUILDDIR% /q /s
+%SPHINXBUILD% -M %1 %SOURCEDIR% %BUILDDIR% %SPHINXOPTS%
+goto end
+
+:help
+%SPHINXBUILD% -M help %SOURCEDIR% %BUILDDIR% %SPHINXOPTS%
+
+:end
+popd
diff --git a/source/_global.rst b/source/_global.rst
new file mode 100644
index 0000000..ca35d38
--- /dev/null
+++ b/source/_global.rst
@@ -0,0 +1,46 @@
+.. Licensed to the Apache Software Foundation (ASF) under one
+   or more contributor license agreements.  See the NOTICE file
+   distributed with this work for additional information#
+   regarding copyright ownership.  The ASF licenses this file
+   to you under the Apache License, Version 2.0 (the
+   "License"); you may not use this file except in compliance
+   with the License.  You may obtain a copy of the License at
+   http://www.apache.org/licenses/LICENSE-2.0
+   Unless required by applicable law or agreed to in writing,
+   software distributed under the License is distributed on an
+   "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+   KIND, either express or implied.  See the License for the
+   specific language governing permissions and limitations
+   under the License.
+
+
+.. This file contain Variables shared across other .rst files in this project
+
+
+.. _CloudStack Installation Guide: http://docs.cloudstack.apache.org/projects/cloudstack-installation
+.. _CloudStack Administrator's Guide: http://docs.cloudstack.apache.org/projects/cloudstack-administration
+.. _CloudStack Apidocs: http://cloudstack.apache.org/docs/api/
+
+.. |documentation_home| replace:: http://docs.cloudstack.apache.org/
+
+.. Latest version systemvm template URL
+.. |sysvm64-url-xen|    replace:: http://download.cloudstack.org/systemvm/4.11/systemvmtemplate-4.11.1-xen.vhd.bz2
+.. |sysvm64-url-kvm|    replace:: http://download.cloudstack.org/systemvm/4.11/systemvmtemplate-4.11.1-kvm.qcow2.bz2
+.. |sysvm64-url-vmware| replace:: http://download.cloudstack.org/systemvm/4.11/systemvmtemplate-4.11.1-vmware.ova
+.. |sysvm64-url-hyperv| replace:: http://download.cloudstack.org/systemvm/4.11/systemvmtemplate-4.11.1-hyperv.vhd.zip
+.. |sysvm64-url-ovm|    replace:: http://download.cloudstack.org/systemvm/4.11/systemvmtemplate-4.11.1-ovm.raw.bz2
+
+.. Version specific: 4.5 systemvm template URL
+.. |acs45-sysvm64-url-xen|    replace:: http://download.cloudstack.org/systemvm/4.5/systemvm64template-4.5-xen.vhd.bz2
+.. |acs45-sysvm64-url-kvm|    replace:: http://download.cloudstack.org/systemvm/4.5/systemvm64template-4.5-kvm.qcow2.bz2
+.. |acs45-sysvm64-url-vmware| replace:: http://download.cloudstack.org/systemvm/4.5/systemvm64template-4.5-vmware.ova
+.. |acs45-sysvm64-url-hyperv| replace:: http://download.cloudstack.org/systemvm/4.5/systemvm64template-4.5-hyperv.vhd.zip
+
+.. Images
+
+
+.. |vpn-icon.png| image:: /_static/images/vpn-icon.png
+.. |sysmanager.png| image:: /_static/images/sysmanager.png
+.. |software-license.png| image:: /_static/images/software-license.png
+.. |change-admin-password.png| image:: /_static/images/change-admin-password.png
+.. |menu_acs_logo| image:: /_static/acslogo.png
\ No newline at end of file
diff --git a/source/_static/acslogo.png b/source/_static/acslogo.png
new file mode 100644
index 0000000..a938231
Binary files /dev/null and b/source/_static/acslogo.png differ
diff --git a/source/_static/images/1000-foot-view.png b/source/_static/images/1000-foot-view.png
new file mode 100644
index 0000000..2fe3c16
Binary files /dev/null and b/source/_static/images/1000-foot-view.png differ
diff --git a/source/_static/images/60recipe.gif b/source/_static/images/60recipe.gif
new file mode 100644
index 0000000..a47a399
Binary files /dev/null and b/source/_static/images/60recipe.gif differ
diff --git a/source/_static/images/CloudStack-ldap-screen1.png b/source/_static/images/CloudStack-ldap-screen1.png
new file mode 100644
index 0000000..46032a4
Binary files /dev/null and b/source/_static/images/CloudStack-ldap-screen1.png differ
diff --git a/source/_static/images/DevCloud-hostonly.png b/source/_static/images/DevCloud-hostonly.png
new file mode 100644
index 0000000..111f93a
Binary files /dev/null and b/source/_static/images/DevCloud-hostonly.png differ
diff --git a/source/_static/images/DevCloud.png b/source/_static/images/DevCloud.png
new file mode 100644
index 0000000..5e83ca9
Binary files /dev/null and b/source/_static/images/DevCloud.png differ
diff --git a/source/_static/images/SnapshotButton.png b/source/_static/images/SnapshotButton.png
new file mode 100644
index 0000000..5217740
Binary files /dev/null and b/source/_static/images/SnapshotButton.png differ
diff --git a/source/_static/images/VMSnapshotButton.png b/source/_static/images/VMSnapshotButton.png
new file mode 100644
index 0000000..5217740
Binary files /dev/null and b/source/_static/images/VMSnapshotButton.png differ
diff --git a/source/_static/images/acslogo.png b/source/_static/images/acslogo.png
new file mode 100644
index 0000000..a938231
Binary files /dev/null and b/source/_static/images/acslogo.png differ
diff --git a/source/_static/images/add-cifs.png b/source/_static/images/add-cifs.png
new file mode 100644
index 0000000..9081f77
Binary files /dev/null and b/source/_static/images/add-cifs.png differ
diff --git a/source/_static/images/add-cluster.png b/source/_static/images/add-cluster.png
new file mode 100644
index 0000000..4b24ec7
Binary files /dev/null and b/source/_static/images/add-cluster.png differ
diff --git a/source/_static/images/add-gateway.png b/source/_static/images/add-gateway.png
new file mode 100644
index 0000000..da8eed9
Binary files /dev/null and b/source/_static/images/add-gateway.png differ
diff --git a/source/_static/images/add-gslb.png b/source/_static/images/add-gslb.png
new file mode 100644
index 0000000..827a913
Binary files /dev/null and b/source/_static/images/add-gslb.png differ
diff --git a/source/_static/images/add-guest-network.png b/source/_static/images/add-guest-network.png
new file mode 100644
index 0000000..5740ab5
Binary files /dev/null and b/source/_static/images/add-guest-network.png differ
diff --git a/source/_static/images/add-ip-range.png b/source/_static/images/add-ip-range.png
new file mode 100644
index 0000000..9f4d9d4
Binary files /dev/null and b/source/_static/images/add-ip-range.png differ
diff --git a/source/_static/images/add-ldap-configuration-ad.png b/source/_static/images/add-ldap-configuration-ad.png
new file mode 100644
index 0000000..d4d3e78
Binary files /dev/null and b/source/_static/images/add-ldap-configuration-ad.png differ
diff --git a/source/_static/images/add-ldap-configuration-openldap.png b/source/_static/images/add-ldap-configuration-openldap.png
new file mode 100644
index 0000000..70ce579
Binary files /dev/null and b/source/_static/images/add-ldap-configuration-openldap.png differ
diff --git a/source/_static/images/add-new-gateway-vpc.png b/source/_static/images/add-new-gateway-vpc.png
new file mode 100644
index 0000000..5145622
Binary files /dev/null and b/source/_static/images/add-new-gateway-vpc.png differ
diff --git a/source/_static/images/add-tier.png b/source/_static/images/add-tier.png
new file mode 100644
index 0000000..0994dbd
Binary files /dev/null and b/source/_static/images/add-tier.png differ
diff --git a/source/_static/images/add-vlan-icon.png b/source/_static/images/add-vlan-icon.png
new file mode 100644
index 0000000..04655dc
Binary files /dev/null and b/source/_static/images/add-vlan-icon.png differ
diff --git a/source/_static/images/add-vm-vpc.png b/source/_static/images/add-vm-vpc.png
new file mode 100644
index 0000000..b2821a6
Binary files /dev/null and b/source/_static/images/add-vm-vpc.png differ
diff --git a/source/_static/images/add-vpc.png b/source/_static/images/add-vpc.png
new file mode 100644
index 0000000..f334862
Binary files /dev/null and b/source/_static/images/add-vpc.png differ
diff --git a/source/_static/images/add-vpn-customer-gateway.png b/source/_static/images/add-vpn-customer-gateway.png
new file mode 100644
index 0000000..fdc3177
Binary files /dev/null and b/source/_static/images/add-vpn-customer-gateway.png differ
diff --git a/source/_static/images/addAccount-icon.png b/source/_static/images/addAccount-icon.png
new file mode 100644
index 0000000..4743dbe
Binary files /dev/null and b/source/_static/images/addAccount-icon.png differ
diff --git a/source/_static/images/addvm-tier-sharednw.png b/source/_static/images/addvm-tier-sharednw.png
new file mode 100644
index 0000000..e60205f
Binary files /dev/null and b/source/_static/images/addvm-tier-sharednw.png differ
diff --git a/source/_static/images/attach-disk-icon.png b/source/_static/images/attach-disk-icon.png
new file mode 100644
index 0000000..5e81d04
Binary files /dev/null and b/source/_static/images/attach-disk-icon.png differ
diff --git a/source/_static/images/autoscale-config.png b/source/_static/images/autoscale-config.png
new file mode 100644
index 0000000..735ae96
Binary files /dev/null and b/source/_static/images/autoscale-config.png differ
diff --git a/source/_static/images/basic-deployment.png b/source/_static/images/basic-deployment.png
new file mode 100644
index 0000000..894a053
Binary files /dev/null and b/source/_static/images/basic-deployment.png differ
diff --git a/source/_static/images/change-admin-password.png b/source/_static/images/change-admin-password.png
new file mode 100644
index 0000000..938e861
Binary files /dev/null and b/source/_static/images/change-admin-password.png differ
diff --git a/source/_static/images/change-affinity-button.png b/source/_static/images/change-affinity-button.png
new file mode 100644
index 0000000..c21ef75
Binary files /dev/null and b/source/_static/images/change-affinity-button.png differ
diff --git a/source/_static/images/change-password.png b/source/_static/images/change-password.png
new file mode 100644
index 0000000..fbb203a
Binary files /dev/null and b/source/_static/images/change-password.png differ
diff --git a/source/_static/images/change-service-icon.png b/source/_static/images/change-service-icon.png
new file mode 100644
index 0000000..780e235
Binary files /dev/null and b/source/_static/images/change-service-icon.png differ
diff --git a/source/_static/images/cifs-primary.png b/source/_static/images/cifs-primary.png
new file mode 100644
index 0000000..4189980
Binary files /dev/null and b/source/_static/images/cifs-primary.png differ
diff --git a/source/_static/images/cifs-ss.png b/source/_static/images/cifs-ss.png
new file mode 100644
index 0000000..5098095
Binary files /dev/null and b/source/_static/images/cifs-ss.png differ
diff --git a/source/_static/images/cloudian-s3_ss_cache.png b/source/_static/images/cloudian-s3_ss_cache.png
new file mode 100644
index 0000000..5d97186
Binary files /dev/null and b/source/_static/images/cloudian-s3_ss_cache.png differ
diff --git a/source/_static/images/cloudian-s3_ss_config.png b/source/_static/images/cloudian-s3_ss_config.png
new file mode 100644
index 0000000..3ad273a
Binary files /dev/null and b/source/_static/images/cloudian-s3_ss_config.png differ
diff --git a/source/_static/images/cloudian-ss_globalopt.png b/source/_static/images/cloudian-ss_globalopt.png
new file mode 100644
index 0000000..d1b9272
Binary files /dev/null and b/source/_static/images/cloudian-ss_globalopt.png differ
diff --git a/source/_static/images/cloudian-tab.png b/source/_static/images/cloudian-tab.png
new file mode 100644
index 0000000..57383e8
Binary files /dev/null and b/source/_static/images/cloudian-tab.png differ
diff --git a/source/_static/images/cluster-overview.png b/source/_static/images/cluster-overview.png
new file mode 100644
index 0000000..18a86c3
Binary files /dev/null and b/source/_static/images/cluster-overview.png differ
diff --git a/source/_static/images/compute-service-offerings.png b/source/_static/images/compute-service-offerings.png
new file mode 100644
index 0000000..88eb6f8
Binary files /dev/null and b/source/_static/images/compute-service-offerings.png differ
diff --git a/source/_static/images/console-icon.png b/source/_static/images/console-icon.png
new file mode 100644
index 0000000..bf28886
Binary files /dev/null and b/source/_static/images/console-icon.png differ
diff --git a/source/_static/images/create-vpn-connection.png b/source/_static/images/create-vpn-connection.png
new file mode 100644
index 0000000..c7d8c15
Binary files /dev/null and b/source/_static/images/create-vpn-connection.png differ
diff --git a/source/_static/images/dedicate-resource-button.png b/source/_static/images/dedicate-resource-button.png
new file mode 100644
index 0000000..0ac38e0
Binary files /dev/null and b/source/_static/images/dedicate-resource-button.png differ
diff --git a/source/_static/images/del-tier.png b/source/_static/images/del-tier.png
new file mode 100644
index 0000000..aa9846c
Binary files /dev/null and b/source/_static/images/del-tier.png differ
diff --git a/source/_static/images/delete-button.png b/source/_static/images/delete-button.png
new file mode 100644
index 0000000..27145ce
Binary files /dev/null and b/source/_static/images/delete-button.png differ
diff --git a/source/_static/images/destroy-instance.png b/source/_static/images/destroy-instance.png
new file mode 100644
index 0000000..aa9846c
Binary files /dev/null and b/source/_static/images/destroy-instance.png differ
diff --git a/source/_static/images/detach-disk-icon.png b/source/_static/images/detach-disk-icon.png
new file mode 100644
index 0000000..536a4f8
Binary files /dev/null and b/source/_static/images/detach-disk-icon.png differ
diff --git a/source/_static/images/dvswitch-config.png b/source/_static/images/dvswitch-config.png
new file mode 100644
index 0000000..edce6e8
Binary files /dev/null and b/source/_static/images/dvswitch-config.png differ
diff --git a/source/_static/images/dvswitchconfig.png b/source/_static/images/dvswitchconfig.png
new file mode 100644
index 0000000..55b1ef7
Binary files /dev/null and b/source/_static/images/dvswitchconfig.png differ
diff --git a/source/_static/images/ec2-s3-configuration.png b/source/_static/images/ec2-s3-configuration.png
new file mode 100644
index 0000000..e9f98f0
Binary files /dev/null and b/source/_static/images/ec2-s3-configuration.png differ
diff --git a/source/_static/images/edit-icon.png b/source/_static/images/edit-icon.png
new file mode 100644
index 0000000..42417e2
Binary files /dev/null and b/source/_static/images/edit-icon.png differ
diff --git a/source/_static/images/edit-traffic-type.png b/source/_static/images/edit-traffic-type.png
new file mode 100644
index 0000000..16cda94
Binary files /dev/null and b/source/_static/images/edit-traffic-type.png differ
diff --git a/source/_static/images/egress-firewall-rule.png b/source/_static/images/egress-firewall-rule.png
new file mode 100644
index 0000000..fa1d8ec
Binary files /dev/null and b/source/_static/images/egress-firewall-rule.png differ
diff --git a/source/_static/images/eip-ns-basiczone.png b/source/_static/images/eip-ns-basiczone.png
new file mode 100644
index 0000000..bc88570
Binary files /dev/null and b/source/_static/images/eip-ns-basiczone.png differ
diff --git a/source/_static/images/enable-disable-autoscale.png b/source/_static/images/enable-disable-autoscale.png
new file mode 100644
index 0000000..ee02ef2
Binary files /dev/null and b/source/_static/images/enable-disable-autoscale.png differ
diff --git a/source/_static/images/enable-disable.png b/source/_static/images/enable-disable.png
new file mode 100644
index 0000000..cab31ae
Binary files /dev/null and b/source/_static/images/enable-disable.png differ
diff --git a/source/_static/images/gslb.png b/source/_static/images/gslb.png
new file mode 100644
index 0000000..f0a04db
Binary files /dev/null and b/source/_static/images/gslb.png differ
diff --git a/source/_static/images/guest-traffic-setup.png b/source/_static/images/guest-traffic-setup.png
new file mode 100644
index 0000000..5250819
Binary files /dev/null and b/source/_static/images/guest-traffic-setup.png differ
diff --git a/source/_static/images/http-access.png b/source/_static/images/http-access.png
new file mode 100644
index 0000000..817f197
Binary files /dev/null and b/source/_static/images/http-access.png differ
diff --git a/source/_static/images/hypervisorcomms-secstorage.png b/source/_static/images/hypervisorcomms-secstorage.png
new file mode 100644
index 0000000..c5c1f8d
Binary files /dev/null and b/source/_static/images/hypervisorcomms-secstorage.png differ
diff --git a/source/_static/images/hypervisorcomms.png b/source/_static/images/hypervisorcomms.png
new file mode 100644
index 0000000..5d4b0ab
Binary files /dev/null and b/source/_static/images/hypervisorcomms.png differ
diff --git a/source/_static/images/icon.svg b/source/_static/images/icon.svg
new file mode 100644
index 0000000..37f94c0
--- /dev/null
+++ b/source/_static/images/icon.svg
@@ -0,0 +1,37 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!--
+Licensed to the Apache Software Foundation (ASF) under one
+or more contributor license agreements.  See the NOTICE file
+distributed with this work for additional information
+regarding copyright ownership.  The ASF licenses this file
+to you under the Apache License, Version 2.0 (the
+"License"); you may not use this file except in compliance
+with the License.  You may obtain a copy of the License at
+
+  http://www.apache.org/licenses/LICENSE-2.0
+
+Unless required by applicable law or agreed to in writing,
+software distributed under the License is distributed on an
+"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+KIND, either express or implied.  See the License for the
+specific language governing permissions and limitations
+under the License.
+-->
+<svg xmlns:svg="http://www.w3.org/2000/svg" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" version="1.0" width="32" height="32" id="svg3017">
+  <defs id="defs3019">
+    <linearGradient id="linearGradient2381">
+      <stop id="stop2383" style="stop-color:#ffffff;stop-opacity:1" offset="0"/>
+      <stop id="stop2385" style="stop-color:#ffffff;stop-opacity:0" offset="1"/>
+    </linearGradient>
+    <linearGradient x1="296.4996" y1="188.81061" x2="317.32471" y2="209.69398" id="linearGradient2371" xlink:href="#linearGradient2381" gradientUnits="userSpaceOnUse" gradientTransform="matrix(0.90776,0,0,0.90776,24.35648,49.24131)"/>
+  </defs>
+  <g transform="matrix(0.437808,-0.437808,0.437808,0.437808,-220.8237,43.55311)" id="g5089">
+    <path d="m 8.4382985,-6.28125 c -0.6073916,0 -4.3132985,5.94886271 -4.3132985,8.25 l 0,26.71875 c 0,0.846384 0.5818159,1.125 1.15625,1.125 l 25.5625,0 c 0.632342,0 1.125001,-0.492658 1.125,-1.125 l 0,-5.21875 0.28125,0 c 0.49684,0 0.906249,-0.409411 0.90625,-0.90625 l 0,-27.9375 c 0,-0.4968398 -0.40941,-0.90625 -0.90625,-0.90625 l -23.8117015,0 z" transform="translate(282.8327,227.1903)" id="path5091" style="fill:#5c5c4f;stroke:#000000;stroke-width:3.23021388;stroke-miterlimit:4;stro [...]
+    <rect width="27.85074" height="29.369793" rx="1.1414107" ry="1.1414107" x="286.96509" y="227.63805" id="rect5093" style="fill:#032c87"/>
+    <path d="m 288.43262,225.43675 25.2418,0 0,29.3698 -26.37615,0.0241 1.13435,-29.39394 z" id="rect5095" style="fill:#ffffff"/>
+    <path d="m 302.44536,251.73726 c 1.38691,7.85917 -0.69311,11.28365 -0.69311,11.28365 2.24384,-1.60762 3.96426,-3.47694 4.90522,-5.736 0.96708,2.19264 1.83294,4.42866 4.27443,5.98941 0,0 -1.59504,-7.2004 -1.71143,-11.53706 l -6.77511,0 z" id="path5097" style="fill:#a70000;fill-opacity:1;stroke-width:2"/>
+    <rect width="25.241802" height="29.736675" rx="0.89682275" ry="0.89682275" x="290.73544" y="220.92249" id="rect5099" style="fill:#809cc9"/>
+    <path d="m 576.47347,725.93939 6.37084,0.41502 0.4069,29.51809 c -1.89202,-1.31785 -6.85427,-3.7608 -8.26232,-1.68101 l 0,-26.76752 c 0,-0.82246 0.66212,-1.48458 1.48458,-1.48458 z" transform="matrix(0.499065,-0.866565,0,1,0,0)" id="rect5101" style="fill:#4573b3;fill-opacity:1"/>
+    <path d="m 293.2599,221.89363 20.73918,0 c 0.45101,0 0.8141,0.3631 0.8141,0.81411 0.21547,6.32836 -19.36824,21.7635 -22.36739,17.59717 l 0,-17.59717 c 0,-0.45101 0.3631,-0.81411 0.81411,-0.81411 z" id="path5103" style="opacity:0.65536726;fill:url(#linearGradient2371);fill-opacity:1"/>
+  </g>
+</svg>
diff --git a/source/_static/images/infrastructure-overview.png b/source/_static/images/infrastructure-overview.png
new file mode 100644
index 0000000..24aeecf
Binary files /dev/null and b/source/_static/images/infrastructure-overview.png differ
diff --git a/source/_static/images/installation-complete.png b/source/_static/images/installation-complete.png
new file mode 100644
index 0000000..4626f86
Binary files /dev/null and b/source/_static/images/installation-complete.png differ
diff --git a/source/_static/images/iso-icon.png b/source/_static/images/iso-icon.png
new file mode 100644
index 0000000..8d547fb
Binary files /dev/null and b/source/_static/images/iso-icon.png differ
diff --git a/source/_static/images/jp1.jpg b/source/_static/images/jp1.jpg
new file mode 100644
index 0000000..1778794
Binary files /dev/null and b/source/_static/images/jp1.jpg differ
diff --git a/source/_static/images/jp2.jpg b/source/_static/images/jp2.jpg
new file mode 100644
index 0000000..3cc804a
Binary files /dev/null and b/source/_static/images/jp2.jpg differ
diff --git a/source/_static/images/large-scale-redundant-setup.png b/source/_static/images/large-scale-redundant-setup.png
new file mode 100644
index 0000000..5d2581a
Binary files /dev/null and b/source/_static/images/large-scale-redundant-setup.png differ
diff --git a/source/_static/images/ldap-config.png b/source/_static/images/ldap-config.png
new file mode 100644
index 0000000..28233d9
Binary files /dev/null and b/source/_static/images/ldap-config.png differ
diff --git a/source/_static/images/mesos-integration-arch.jpg b/source/_static/images/mesos-integration-arch.jpg
new file mode 100644
index 0000000..e69de29
diff --git a/source/_static/images/metric-view.png b/source/_static/images/metric-view.png
new file mode 100644
index 0000000..bbc6c98
Binary files /dev/null and b/source/_static/images/metric-view.png differ
diff --git a/source/_static/images/migrate-instance.png b/source/_static/images/migrate-instance.png
new file mode 100644
index 0000000..25ff572
Binary files /dev/null and b/source/_static/images/migrate-instance.png differ
diff --git a/source/_static/images/monkey.png b/source/_static/images/monkey.png
new file mode 100644
index 0000000..37928d5
Binary files /dev/null and b/source/_static/images/monkey.png differ
diff --git a/source/_static/images/multi-node-management-server.png b/source/_static/images/multi-node-management-server.png
new file mode 100644
index 0000000..5cf5ed5
Binary files /dev/null and b/source/_static/images/multi-node-management-server.png differ
diff --git a/source/_static/images/multi-site-deployment.png b/source/_static/images/multi-site-deployment.png
new file mode 100644
index 0000000..f3ae5bb
Binary files /dev/null and b/source/_static/images/multi-site-deployment.png differ
diff --git a/source/_static/images/multi-tier-app.png b/source/_static/images/multi-tier-app.png
new file mode 100644
index 0000000..cec1122
Binary files /dev/null and b/source/_static/images/multi-tier-app.png differ
diff --git a/source/_static/images/network-acl.png b/source/_static/images/network-acl.png
new file mode 100644
index 0000000..5602827
Binary files /dev/null and b/source/_static/images/network-acl.png differ
diff --git a/source/_static/images/network-setup-zone.png b/source/_static/images/network-setup-zone.png
new file mode 100644
index 0000000..8324ff8
Binary files /dev/null and b/source/_static/images/network-setup-zone.png differ
diff --git a/source/_static/images/network-singlepod.png b/source/_static/images/network-singlepod.png
new file mode 100644
index 0000000..e1214ea
Binary files /dev/null and b/source/_static/images/network-singlepod.png differ
diff --git a/source/_static/images/networking-egress-rule.png b/source/_static/images/networking-egress-rule.png
new file mode 100644
index 0000000..edf1f6d
Binary files /dev/null and b/source/_static/images/networking-egress-rule.png differ
diff --git a/source/_static/images/networking-in-a-pod.png b/source/_static/images/networking-in-a-pod.png
new file mode 100644
index 0000000..bf73171
Binary files /dev/null and b/source/_static/images/networking-in-a-pod.png differ
diff --git a/source/_static/images/networking-in-a-zone.png b/source/_static/images/networking-in-a-zone.png
new file mode 100644
index 0000000..fb740da
Binary files /dev/null and b/source/_static/images/networking-in-a-zone.png differ
diff --git a/source/_static/images/networking-infra-traffic-labels.png b/source/_static/images/networking-infra-traffic-labels.png
new file mode 100644
index 0000000..e029d7d
Binary files /dev/null and b/source/_static/images/networking-infra-traffic-labels.png differ
diff --git a/source/_static/images/networking-ingress-rule.png b/source/_static/images/networking-ingress-rule.png
new file mode 100644
index 0000000..8b1af22
Binary files /dev/null and b/source/_static/images/networking-ingress-rule.png differ
diff --git a/source/_static/images/networking-zone-traffic-labels.png b/source/_static/images/networking-zone-traffic-labels.png
new file mode 100644
index 0000000..1587c2b
Binary files /dev/null and b/source/_static/images/networking-zone-traffic-labels.png differ
diff --git a/source/_static/images/nic-bonding-and-multipath-io.png b/source/_static/images/nic-bonding-and-multipath-io.png
new file mode 100644
index 0000000..0fe60b6
Binary files /dev/null and b/source/_static/images/nic-bonding-and-multipath-io.png differ
diff --git a/source/_static/images/nuage_iso_net_off.png b/source/_static/images/nuage_iso_net_off.png
new file mode 100644
index 0000000..2ebb03b
Binary files /dev/null and b/source/_static/images/nuage_iso_net_off.png differ
diff --git a/source/_static/images/nuage_kvm_traffic_label.jpg b/source/_static/images/nuage_kvm_traffic_label.jpg
new file mode 100644
index 0000000..e81c0f5
Binary files /dev/null and b/source/_static/images/nuage_kvm_traffic_label.jpg differ
diff --git a/source/_static/images/nuage_sha_net_off.png b/source/_static/images/nuage_sha_net_off.png
new file mode 100644
index 0000000..71ddcfc
Binary files /dev/null and b/source/_static/images/nuage_sha_net_off.png differ
diff --git a/source/_static/images/nuage_source_nat_net_off.png b/source/_static/images/nuage_source_nat_net_off.png
new file mode 100644
index 0000000..00f7955
Binary files /dev/null and b/source/_static/images/nuage_source_nat_net_off.png differ
diff --git a/source/_static/images/nuage_underlay_api_usage.png b/source/_static/images/nuage_underlay_api_usage.png
new file mode 100644
index 0000000..6761dc8
Binary files /dev/null and b/source/_static/images/nuage_underlay_api_usage.png differ
diff --git a/source/_static/images/nuage_vmware_traffic_label.jpg b/source/_static/images/nuage_vmware_traffic_label.jpg
new file mode 100644
index 0000000..6f7a7c1
Binary files /dev/null and b/source/_static/images/nuage_vmware_traffic_label.jpg differ
diff --git a/source/_static/images/nuage_vpc_net_off.png b/source/_static/images/nuage_vpc_net_off.png
new file mode 100644
index 0000000..b45e8fe
Binary files /dev/null and b/source/_static/images/nuage_vpc_net_off.png differ
diff --git a/source/_static/images/nuage_vpc_off.png b/source/_static/images/nuage_vpc_off.png
new file mode 100644
index 0000000..a353e2f
Binary files /dev/null and b/source/_static/images/nuage_vpc_off.png differ
diff --git a/source/_static/images/nuage_vsd_device_add.png b/source/_static/images/nuage_vsd_device_add.png
new file mode 100644
index 0000000..60513d2
Binary files /dev/null and b/source/_static/images/nuage_vsd_device_add.png differ
diff --git a/source/_static/images/nuage_vsp_isolation_method_setting.png b/source/_static/images/nuage_vsp_isolation_method_setting.png
new file mode 100644
index 0000000..9dabf9a
Binary files /dev/null and b/source/_static/images/nuage_vsp_isolation_method_setting.png differ
diff --git a/source/_static/images/nuage_vsp_nsp_enable.png b/source/_static/images/nuage_vsp_nsp_enable.png
new file mode 100644
index 0000000..df7f0b4
Binary files /dev/null and b/source/_static/images/nuage_vsp_nsp_enable.png differ
diff --git a/source/_static/images/nuage_vsp_nsp_status.png b/source/_static/images/nuage_vsp_nsp_status.png
new file mode 100644
index 0000000..c8dd02e
Binary files /dev/null and b/source/_static/images/nuage_vsp_nsp_status.png differ
diff --git a/source/_static/images/nuage_vsp_vpc_off.png b/source/_static/images/nuage_vsp_vpc_off.png
new file mode 100644
index 0000000..b1c4f29
Binary files /dev/null and b/source/_static/images/nuage_vsp_vpc_off.png differ
diff --git a/source/_static/images/nvp-add-controller.png b/source/_static/images/nvp-add-controller.png
new file mode 100644
index 0000000..e02d31f
Binary files /dev/null and b/source/_static/images/nvp-add-controller.png differ
diff --git a/source/_static/images/nvp-enable-provider.png b/source/_static/images/nvp-enable-provider.png
new file mode 100644
index 0000000..0f2d02d
Binary files /dev/null and b/source/_static/images/nvp-enable-provider.png differ
diff --git a/source/_static/images/nvp-network-offering.png b/source/_static/images/nvp-network-offering.png
new file mode 100644
index 0000000..c2d25c4
Binary files /dev/null and b/source/_static/images/nvp-network-offering.png differ
diff --git a/source/_static/images/nvp-physical-network-stt.png b/source/_static/images/nvp-physical-network-stt.png
new file mode 100644
index 0000000..2ce7853
Binary files /dev/null and b/source/_static/images/nvp-physical-network-stt.png differ
diff --git a/source/_static/images/nvp-vpc-offering-edit.png b/source/_static/images/nvp-vpc-offering-edit.png
new file mode 100644
index 0000000..ff235e2
Binary files /dev/null and b/source/_static/images/nvp-vpc-offering-edit.png differ
diff --git a/source/_static/images/ovs-network-offering.png b/source/_static/images/ovs-network-offering.png
new file mode 100644
index 0000000..750c5f0
Binary files /dev/null and b/source/_static/images/ovs-network-offering.png differ
diff --git a/source/_static/images/ovs-physical-network-gre-enable.png b/source/_static/images/ovs-physical-network-gre-enable.png
new file mode 100644
index 0000000..40c5418
Binary files /dev/null and b/source/_static/images/ovs-physical-network-gre-enable.png differ
diff --git a/source/_static/images/ovs-physical-network-gre.png b/source/_static/images/ovs-physical-network-gre.png
new file mode 100644
index 0000000..1e8bb00
Binary files /dev/null and b/source/_static/images/ovs-physical-network-gre.png differ
diff --git a/source/_static/images/packt.png b/source/_static/images/packt.png
new file mode 100644
index 0000000..53f8a47
Binary files /dev/null and b/source/_static/images/packt.png differ
diff --git a/source/_static/images/parallel-mode.png b/source/_static/images/parallel-mode.png
new file mode 100644
index 0000000..3b67a17
Binary files /dev/null and b/source/_static/images/parallel-mode.png differ
diff --git a/source/_static/images/plugin1.jpg b/source/_static/images/plugin1.jpg
new file mode 100644
index 0000000..970233d
Binary files /dev/null and b/source/_static/images/plugin1.jpg differ
diff --git a/source/_static/images/plugin2.jpg b/source/_static/images/plugin2.jpg
new file mode 100644
index 0000000..9c8a610
Binary files /dev/null and b/source/_static/images/plugin2.jpg differ
diff --git a/source/_static/images/plugin3.jpg b/source/_static/images/plugin3.jpg
new file mode 100644
index 0000000..07fae79
Binary files /dev/null and b/source/_static/images/plugin3.jpg differ
diff --git a/source/_static/images/plugin4.jpg b/source/_static/images/plugin4.jpg
new file mode 100644
index 0000000..2bcec9f
Binary files /dev/null and b/source/_static/images/plugin4.jpg differ
diff --git a/source/_static/images/plugin_intro.jpg b/source/_static/images/plugin_intro.jpg
new file mode 100644
index 0000000..113ffb3
Binary files /dev/null and b/source/_static/images/plugin_intro.jpg differ
diff --git a/source/_static/images/pod-overview.png b/source/_static/images/pod-overview.png
new file mode 100644
index 0000000..c180060
Binary files /dev/null and b/source/_static/images/pod-overview.png differ
diff --git a/source/_static/images/provisioning-overview.png b/source/_static/images/provisioning-overview.png
new file mode 100644
index 0000000..25cc97e
Binary files /dev/null and b/source/_static/images/provisioning-overview.png differ
diff --git a/source/_static/images/region-overview.png b/source/_static/images/region-overview.png
new file mode 100644
index 0000000..528445c
Binary files /dev/null and b/source/_static/images/region-overview.png differ
diff --git a/source/_static/images/release-ip-icon.png b/source/_static/images/release-ip-icon.png
new file mode 100644
index 0000000..aa9846c
Binary files /dev/null and b/source/_static/images/release-ip-icon.png differ
diff --git a/source/_static/images/remove-nic.png b/source/_static/images/remove-nic.png
new file mode 100644
index 0000000..27145ce
Binary files /dev/null and b/source/_static/images/remove-nic.png differ
diff --git a/source/_static/images/remove-tier.png b/source/_static/images/remove-tier.png
new file mode 100644
index 0000000..e14d08f
Binary files /dev/null and b/source/_static/images/remove-tier.png differ
diff --git a/source/_static/images/remove-vpc.png b/source/_static/images/remove-vpc.png
new file mode 100644
index 0000000..aa9846c
Binary files /dev/null and b/source/_static/images/remove-vpc.png differ
diff --git a/source/_static/images/remove-vpn.png b/source/_static/images/remove-vpn.png
new file mode 100644
index 0000000..27145ce
Binary files /dev/null and b/source/_static/images/remove-vpn.png differ
diff --git a/source/_static/images/replace-acl-icon.png b/source/_static/images/replace-acl-icon.png
new file mode 100644
index 0000000..ae953ba
Binary files /dev/null and b/source/_static/images/replace-acl-icon.png differ
diff --git a/source/_static/images/replace-acl-list.png b/source/_static/images/replace-acl-list.png
new file mode 100644
index 0000000..3375017
Binary files /dev/null and b/source/_static/images/replace-acl-list.png differ
diff --git a/source/_static/images/reset-vpn.png b/source/_static/images/reset-vpn.png
new file mode 100644
index 0000000..04655dc
Binary files /dev/null and b/source/_static/images/reset-vpn.png differ
diff --git a/source/_static/images/resize-volume-icon.png b/source/_static/images/resize-volume-icon.png
new file mode 100644
index 0000000..4849902
Binary files /dev/null and b/source/_static/images/resize-volume-icon.png differ
diff --git a/source/_static/images/resize-volume.png b/source/_static/images/resize-volume.png
new file mode 100644
index 0000000..6195623
Binary files /dev/null and b/source/_static/images/resize-volume.png differ
diff --git a/source/_static/images/restart-vpc.png b/source/_static/images/restart-vpc.png
new file mode 100644
index 0000000..04655dc
Binary files /dev/null and b/source/_static/images/restart-vpc.png differ
diff --git a/source/_static/images/revert-vm.png b/source/_static/images/revert-vm.png
new file mode 100644
index 0000000..04655dc
Binary files /dev/null and b/source/_static/images/revert-vm.png differ
diff --git a/source/_static/images/s3-ss.png b/source/_static/images/s3-ss.png
new file mode 100644
index 0000000..bd7cdf2
Binary files /dev/null and b/source/_static/images/s3-ss.png differ
diff --git a/source/_static/images/search-button.png b/source/_static/images/search-button.png
new file mode 100644
index 0000000..f329aef
Binary files /dev/null and b/source/_static/images/search-button.png differ
diff --git a/source/_static/images/select-vm-staticnat-vpc.png b/source/_static/images/select-vm-staticnat-vpc.png
new file mode 100644
index 0000000..12fde26
Binary files /dev/null and b/source/_static/images/select-vm-staticnat-vpc.png differ
diff --git a/source/_static/images/separate-storage-network.png b/source/_static/images/separate-storage-network.png
new file mode 100644
index 0000000..24dbbef
Binary files /dev/null and b/source/_static/images/separate-storage-network.png differ
diff --git a/source/_static/images/set-default-nic.png b/source/_static/images/set-default-nic.png
new file mode 100644
index 0000000..f329aef
Binary files /dev/null and b/source/_static/images/set-default-nic.png differ
diff --git a/source/_static/images/small-scale-deployment.png b/source/_static/images/small-scale-deployment.png
new file mode 100644
index 0000000..1c88520
Binary files /dev/null and b/source/_static/images/small-scale-deployment.png differ
diff --git a/source/_static/images/software-license.png b/source/_static/images/software-license.png
new file mode 100644
index 0000000..67aa255
Binary files /dev/null and b/source/_static/images/software-license.png differ
diff --git a/source/_static/images/stop-instance-icon.png b/source/_static/images/stop-instance-icon.png
new file mode 100644
index 0000000..209afce
Binary files /dev/null and b/source/_static/images/stop-instance-icon.png differ
diff --git a/source/_static/images/subnetting_storage.png b/source/_static/images/subnetting_storage.png
new file mode 100644
index 0000000..a6f47d6
Binary files /dev/null and b/source/_static/images/subnetting_storage.png differ
diff --git a/source/_static/images/suspend-icon.png b/source/_static/images/suspend-icon.png
new file mode 100644
index 0000000..cab31ae
Binary files /dev/null and b/source/_static/images/suspend-icon.png differ
diff --git a/source/_static/images/sysmanager.png b/source/_static/images/sysmanager.png
new file mode 100644
index 0000000..5b9df34
Binary files /dev/null and b/source/_static/images/sysmanager.png differ
diff --git a/source/_static/images/traffic-type.png b/source/_static/images/traffic-type.png
new file mode 100644
index 0000000..10d5ddb
Binary files /dev/null and b/source/_static/images/traffic-type.png differ
diff --git a/source/_static/images/update-ssl-icon.png b/source/_static/images/update-ssl-icon.png
new file mode 100644
index 0000000..f5f923d
Binary files /dev/null and b/source/_static/images/update-ssl-icon.png differ
diff --git a/source/_static/images/update-ssl.png b/source/_static/images/update-ssl.png
new file mode 100644
index 0000000..2f2ee53
Binary files /dev/null and b/source/_static/images/update-ssl.png differ
diff --git a/source/_static/images/vds-name.png b/source/_static/images/vds-name.png
new file mode 100644
index 0000000..bf5b4fc
Binary files /dev/null and b/source/_static/images/vds-name.png differ
diff --git a/source/_static/images/view-console-button.png b/source/_static/images/view-console-button.png
new file mode 100644
index 0000000..b321cea
Binary files /dev/null and b/source/_static/images/view-console-button.png differ
diff --git a/source/_static/images/view-systemvm-details.png b/source/_static/images/view-systemvm-details.png
new file mode 100644
index 0000000..bce270b
Binary files /dev/null and b/source/_static/images/view-systemvm-details.png differ
diff --git a/source/_static/images/vm-lifecycle.png b/source/_static/images/vm-lifecycle.png
new file mode 100644
index 0000000..97823fc
Binary files /dev/null and b/source/_static/images/vm-lifecycle.png differ
diff --git a/source/_static/images/vmware-increase-ports.png b/source/_static/images/vmware-increase-ports.png
new file mode 100644
index 0000000..fe96815
Binary files /dev/null and b/source/_static/images/vmware-increase-ports.png differ
diff --git a/source/_static/images/vmware-iscsi-datastore.png b/source/_static/images/vmware-iscsi-datastore.png
new file mode 100644
index 0000000..9f6b33f
Binary files /dev/null and b/source/_static/images/vmware-iscsi-datastore.png differ
diff --git a/source/_static/images/vmware-iscsi-general.png b/source/_static/images/vmware-iscsi-general.png
new file mode 100644
index 0000000..863602b
Binary files /dev/null and b/source/_static/images/vmware-iscsi-general.png differ
diff --git a/source/_static/images/vmware-iscsi-initiator-properties.png b/source/_static/images/vmware-iscsi-initiator-properties.png
new file mode 100644
index 0000000..1fab031
Binary files /dev/null and b/source/_static/images/vmware-iscsi-initiator-properties.png differ
diff --git a/source/_static/images/vmware-iscsi-initiator.png b/source/_static/images/vmware-iscsi-initiator.png
new file mode 100644
index 0000000..a9a8301
Binary files /dev/null and b/source/_static/images/vmware-iscsi-initiator.png differ
diff --git a/source/_static/images/vmware-iscsi-target-add.png b/source/_static/images/vmware-iscsi-target-add.png
new file mode 100644
index 0000000..f016da7
Binary files /dev/null and b/source/_static/images/vmware-iscsi-target-add.png differ
diff --git a/source/_static/images/vmware-mgt-network-properties.png b/source/_static/images/vmware-mgt-network-properties.png
new file mode 100644
index 0000000..9141af9
Binary files /dev/null and b/source/_static/images/vmware-mgt-network-properties.png differ
diff --git a/source/_static/images/vmware-nexus-add-cluster.png b/source/_static/images/vmware-nexus-add-cluster.png
new file mode 100644
index 0000000..7c1dd73
Binary files /dev/null and b/source/_static/images/vmware-nexus-add-cluster.png differ
diff --git a/source/_static/images/vmware-nexus-port-profile.png b/source/_static/images/vmware-nexus-port-profile.png
new file mode 100644
index 0000000..19b264f
Binary files /dev/null and b/source/_static/images/vmware-nexus-port-profile.png differ
diff --git a/source/_static/images/vmware-physical-network.png b/source/_static/images/vmware-physical-network.png
new file mode 100644
index 0000000..a7495c7
Binary files /dev/null and b/source/_static/images/vmware-physical-network.png differ
diff --git a/source/_static/images/vmware-vswitch-properties.png b/source/_static/images/vmware-vswitch-properties.png
new file mode 100644
index 0000000..bc247d2
Binary files /dev/null and b/source/_static/images/vmware-vswitch-properties.png differ
diff --git a/source/_static/images/vpc-lb.png b/source/_static/images/vpc-lb.png
new file mode 100644
index 0000000..4269e8b
Binary files /dev/null and b/source/_static/images/vpc-lb.png differ
diff --git a/source/_static/images/vpc-setting.png b/source/_static/images/vpc-setting.png
new file mode 100644
index 0000000..782299e
Binary files /dev/null and b/source/_static/images/vpc-setting.png differ
diff --git a/source/_static/images/vpn-icon.png b/source/_static/images/vpn-icon.png
new file mode 100644
index 0000000..2ac12f7
Binary files /dev/null and b/source/_static/images/vpn-icon.png differ
diff --git a/source/_static/images/vpn/osxvpn_connected.png b/source/_static/images/vpn/osxvpn_connected.png
new file mode 100644
index 0000000..768f7c4
Binary files /dev/null and b/source/_static/images/vpn/osxvpn_connected.png differ
diff --git a/source/_static/images/vpn/osxvpn_form1.png b/source/_static/images/vpn/osxvpn_form1.png
new file mode 100644
index 0000000..5a9b685
Binary files /dev/null and b/source/_static/images/vpn/osxvpn_form1.png differ
diff --git a/source/_static/images/vpn/osxvpn_form2.png b/source/_static/images/vpn/osxvpn_form2.png
new file mode 100644
index 0000000..fd30d80
Binary files /dev/null and b/source/_static/images/vpn/osxvpn_form2.png differ
diff --git a/source/_static/images/vpn/osxvpn_form3.png b/source/_static/images/vpn/osxvpn_form3.png
new file mode 100644
index 0000000..2fdbdff
Binary files /dev/null and b/source/_static/images/vpn/osxvpn_form3.png differ
diff --git a/source/_static/images/vpn/osxvpn_netconf.png b/source/_static/images/vpn/osxvpn_netconf.png
new file mode 100644
index 0000000..a5a22c0
Binary files /dev/null and b/source/_static/images/vpn/osxvpn_netconf.png differ
diff --git a/source/_static/images/vpn/win1.png b/source/_static/images/vpn/win1.png
new file mode 100644
index 0000000..c9bb893
Binary files /dev/null and b/source/_static/images/vpn/win1.png differ
diff --git a/source/_static/images/vpn/win10.png b/source/_static/images/vpn/win10.png
new file mode 100644
index 0000000..2cbe591
Binary files /dev/null and b/source/_static/images/vpn/win10.png differ
diff --git a/source/_static/images/vpn/win11.png b/source/_static/images/vpn/win11.png
new file mode 100644
index 0000000..cf95426
Binary files /dev/null and b/source/_static/images/vpn/win11.png differ
diff --git a/source/_static/images/vpn/win12.png b/source/_static/images/vpn/win12.png
new file mode 100644
index 0000000..61ba08c
Binary files /dev/null and b/source/_static/images/vpn/win12.png differ
diff --git a/source/_static/images/vpn/win13.png b/source/_static/images/vpn/win13.png
new file mode 100644
index 0000000..d5a990f
Binary files /dev/null and b/source/_static/images/vpn/win13.png differ
diff --git a/source/_static/images/vpn/win14.png b/source/_static/images/vpn/win14.png
new file mode 100644
index 0000000..2d6e93c
Binary files /dev/null and b/source/_static/images/vpn/win14.png differ
diff --git a/source/_static/images/vpn/win2.png b/source/_static/images/vpn/win2.png
new file mode 100644
index 0000000..f30ef69
Binary files /dev/null and b/source/_static/images/vpn/win2.png differ
diff --git a/source/_static/images/vpn/win3.png b/source/_static/images/vpn/win3.png
new file mode 100644
index 0000000..bc0dc91
Binary files /dev/null and b/source/_static/images/vpn/win3.png differ
diff --git a/source/_static/images/vpn/win4.png b/source/_static/images/vpn/win4.png
new file mode 100644
index 0000000..1599f58
Binary files /dev/null and b/source/_static/images/vpn/win4.png differ
diff --git a/source/_static/images/vpn/win5.png b/source/_static/images/vpn/win5.png
new file mode 100644
index 0000000..d2d5f7a
Binary files /dev/null and b/source/_static/images/vpn/win5.png differ
diff --git a/source/_static/images/vpn/win6.png b/source/_static/images/vpn/win6.png
new file mode 100644
index 0000000..cb27870
Binary files /dev/null and b/source/_static/images/vpn/win6.png differ
diff --git a/source/_static/images/vpn/win7.png b/source/_static/images/vpn/win7.png
new file mode 100644
index 0000000..e601f15
Binary files /dev/null and b/source/_static/images/vpn/win7.png differ
diff --git a/source/_static/images/vpn/win8.png b/source/_static/images/vpn/win8.png
new file mode 100644
index 0000000..4ab5db5
Binary files /dev/null and b/source/_static/images/vpn/win8.png differ
diff --git a/source/_static/images/vpn/win9.png b/source/_static/images/vpn/win9.png
new file mode 100644
index 0000000..e276f5f
Binary files /dev/null and b/source/_static/images/vpn/win9.png differ
diff --git a/source/_static/images/vr-upgrade.png b/source/_static/images/vr-upgrade.png
new file mode 100644
index 0000000..42417e2
Binary files /dev/null and b/source/_static/images/vr-upgrade.png differ
diff --git a/source/_static/images/vsphere-client.png b/source/_static/images/vsphere-client.png
new file mode 100644
index 0000000..2acc8b8
Binary files /dev/null and b/source/_static/images/vsphere-client.png differ
diff --git a/source/_static/images/vxlan-physicalnetwork.png b/source/_static/images/vxlan-physicalnetwork.png
new file mode 100644
index 0000000..eb06fcd
Binary files /dev/null and b/source/_static/images/vxlan-physicalnetwork.png differ
diff --git a/source/_static/images/vxlan-trafficlabel.png b/source/_static/images/vxlan-trafficlabel.png
new file mode 100644
index 0000000..916e944
Binary files /dev/null and b/source/_static/images/vxlan-trafficlabel.png differ
diff --git a/source/_static/images/vxlan-vniconfig.png b/source/_static/images/vxlan-vniconfig.png
new file mode 100644
index 0000000..c7372a0
Binary files /dev/null and b/source/_static/images/vxlan-vniconfig.png differ
diff --git a/source/_static/images/workloads.png b/source/_static/images/workloads.png
new file mode 100644
index 0000000..a8334d9
Binary files /dev/null and b/source/_static/images/workloads.png differ
diff --git a/source/_static/images/zone-overview.png b/source/_static/images/zone-overview.png
new file mode 100644
index 0000000..24aeecf
Binary files /dev/null and b/source/_static/images/zone-overview.png differ
diff --git a/source/_static/theme_overrides.css b/source/_static/theme_overrides.css
new file mode 100644
index 0000000..f5c5a5e
--- /dev/null
+++ b/source/_static/theme_overrides.css
@@ -0,0 +1,18 @@
+/* override nav-search background */
+
+/* override table width restrictions */
+.wy-table-responsive table td, .wy-table-responsive table th {
+    white-space: normal;
+}
+
+.wy-table-responsive {
+    margin-bottom: 24px;
+    max-width: 100%;
+    overflow: visible;
+}
+
+/*
+div[class^="highlight"] pre {
+  font-size:10px
+}
+*/
\ No newline at end of file
diff --git a/source/adminguide/accounts.rst b/source/adminguide/accounts.rst
new file mode 100644
index 0000000..3fbc97f
--- /dev/null
+++ b/source/adminguide/accounts.rst
@@ -0,0 +1,437 @@
+.. Licensed to the Apache Software Foundation (ASF) under one
+   or more contributor license agreements.  See the NOTICE file
+   distributed with this work for additional information#
+   regarding copyright ownership.  The ASF licenses this file
+   to you under the Apache License, Version 2.0 (the
+   "License"); you may not use this file except in compliance
+   with the License.  You may obtain a copy of the License at
+   http://www.apache.org/licenses/LICENSE-2.0
+   Unless required by applicable law or agreed to in writing,
+   software distributed under the License is distributed on an
+   "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+   KIND, either express or implied.  See the License for the
+   specific language governing permissions and limitations
+   under the License.
+ 
+
+Roles, Accounts, Users, and Domains
+-----------------------------------
+
+Roles
+~~~~~
+
+A role represents a set of allowed functions. All CloudStack accounts have a
+role attached to them that enforce access rules on them to be allowed or
+disallowed to make an API request. Typically there are four default roles:
+root admin, resource admin, domain admin and user.
+
+
+Accounts
+~~~~~~~~
+
+An account typically represents a customer of the service provider or a
+department in a large organization. Multiple users can exist in an
+account.
+
+
+Domains
+~~~~~~~
+
+Accounts are grouped by domains. Domains usually contain multiple
+accounts that have some logical relationship to each other and a set of
+delegated administrators with some authority over the domain and its
+subdomains. For example, a service provider with several resellers could
+create a domain for each reseller.
+
+For each account created, the Cloud installation creates three different
+types of user accounts: root administrator, domain administrator, and
+user.
+
+
+Users
+~~~~~
+
+Users are like aliases in the account. Users in the same account are not
+isolated from each other, but they are isolated from users in other
+accounts. Most installations need not surface the notion of users; they
+just have one user per account. The same user cannot belong to multiple
+accounts.
+
+Username is unique in a domain across accounts in that domain. The same
+username can exist in other domains, including sub-domains. Domain name
+can repeat only if the full pathname from root is unique. For example,
+you can create root/d1, as well as root/foo/d1, and root/sales/d1.
+
+Administrators are accounts with special privileges in the system. There
+may be multiple administrators in the system. Administrators can create
+or delete other administrators, and change the password for any user in
+the system.
+
+
+Domain Administrators
+~~~~~~~~~~~~~~~~~~~~~
+
+Domain administrators can perform administrative operations for users
+who belong to that domain. Domain administrators do not have visibility
+into physical servers or other domains.
+
+
+Root Administrator
+~~~~~~~~~~~~~~~~~~
+
+Root administrators have complete access to the system, including
+managing templates, service offerings, customer care administrators, and
+domains
+
+
+Resource Ownership
+~~~~~~~~~~~~~~~~~~
+
+Resources belong to the account, not individual users in that account.
+For example, billing, resource limits, and so on are maintained by the
+account, not the users. A user can operate on any resource in the
+account provided the user has privileges for that operation. The
+privileges are determined by the role. A root administrator can change
+the ownership of any virtual machine from one account to any other
+account by using the assignVirtualMachine API. A domain or sub-domain
+administrator can do the same for VMs within the domain from one account
+to any other account in the domain or any of its sub-domains.
+
+.. _using-dynamics-roles:
+
+Using Dynamic Roles
+-------------------
+
+In addition to the four default roles, the dynamic role-based API checker feature
+allows CloudStack root admins to create new roles with customized permissions.
+The allow/deny rules can be configured dynamically during runtime without
+restarting the management server(s).
+
+For backward compatiblity, all roles resolve to one of the four role types:
+admin, resource admin, domain admin and user. A new role can be created using
+the roles tab in the UI and specifying a name, a role type and optionally a
+description.
+
+Role specific rules can be configured through the rules tab on role specific
+details page. A rule is either an API name or a wildcard string that are one of
+allow or deny permission and optionally a description.
+
+When a user makes an API request, the backend checks the requested API against
+configured rules (in the order the rules were configured) for the caller
+user-account's role. It will iterate through the rules and would allow the
+API request if the API matches an allow rule, else if it matches a deny rule
+it would deny the request. Next, if the request API fails to match any of
+the configured rules it would allow if the requested API's default authorized
+annotaions allow that user role type and finally deny the user API request
+if it fails to be explicitly allowed/denied by the role permission rules or the
+default API authorize annotations. Note: to avoid root admin being locked
+out of the system, all root admin accounts are allowed all APIs.
+
+The dynamic-roles feature is enabled by default only for all new CloudStack
+installations since version `4.9.x <https://cwiki.apache.org/confluence/display/CLOUDSTACK/Dynamic+Role+Based+API+Access+Checker+for+CloudStack>`_.
+
+After an upgrade, existing deployments can be migrated to use this feature by
+running a migration tool by the CloudStack admin. The migration tool is located
+at ``/usr/share/cloudstack-common/scripts/util/migrate-dynamicroles.py``.
+
+**NOTE: If you have not changed your commands.properties file at any time, then 
+it is recommended to use the -D (default) option as otherwise new API commands may 
+not be added to the dynamic roles database.**
+
+During migration, this tool enables an internal flag in the database,
+copies existing static role-based rules from provided commands.properties file
+(typically at ``/etc/cloudstack/management/commands.properties``) to the database
+and renames the commands.properties file (typically to
+/etc/cloudstack/management/commands.properties.deprecated). The migration
+process does not require restarting the management server(s).
+
+Usage: ``migrate-dynamicroles.py`` [options] [-h for help]
+
+Options:
+
+-b DB
+    The name of the database, default: cloud
+-u USER
+    User name a MySQL user with privileges on cloud database, default: cloud
+-p PASSWORD
+    Password of a MySQL user with privileges on cloud database
+-H HOST
+    Host or IP of the MySQL server
+-P PORT
+    Host or IP of the MySQL server, default: 3306
+-f FILE
+    The commands.properties file, default: /etc/cloudstack/management/commands.properties
+-d
+    Dry run and debug operations this tool will perform
+-D
+    Use the default configuration for Dynamic Roles (does not import commands.properties)
+
+
+Example:
+ 
+
+.. parsed-literal::
+
+   sudo python /usr/share/cloudstack-common/scripts/util/migrate-dynamicroles.py -u cloud -p cloud -H localhost -P 3306 -f /etc/cloudstack/management/commands.properties
+
+   sudo python /usr/share/cloudstack-common/scripts/util/migrate-dynamicroles.py -u cloud -p cloud -H localhost -P 3306 -D
+
+If you've multiple management servers, remove or rename the commands.properties
+file on all management servers typically in /etc/cloudstack/management path,
+after running the migration tool for the first management server
+
+
+Dedicating Resources to Accounts and Domains
+--------------------------------------------
+
+The root administrator can dedicate resources to a specific domain or
+account that needs private infrastructure for additional security or
+performance guarantees. A zone, pod, cluster, or host can be reserved by
+the root administrator for a specific domain or account. Only users in
+that domain or its subdomain may use the infrastructure. For example,
+only users in a given domain can create guests in a zone dedicated to
+that domain.
+
+There are several types of dedication available:
+
+-  Explicit dedication. A zone, pod, cluster, or host is dedicated to an
+   account or domain by the root administrator during initial deployment
+   and configuration.
+
+-  Strict implicit dedication. A host will not be shared across multiple
+   accounts. For example, strict implicit dedication is useful for
+   deployment of certain types of applications, such as desktops, where
+   no host can be shared between different accounts without violating
+   the desktop software's terms of license.
+
+-  Preferred implicit dedication. The VM will be deployed in dedicated
+   infrastructure if possible. Otherwise, the VM can be deployed in
+   shared infrastructure.
+
+
+How to Dedicate a Zone, Cluster, Pod, or Host to an Account or Domain
+----------------------------------------------------------------------
+
+For explicit dedication: When deploying a new zone, pod, cluster, or
+host, the root administrator can click the Dedicated checkbox, then
+choose a domain or account to own the resource.
+
+To explicitly dedicate an existing zone, pod, cluster, or host: log in
+as the root admin, find the resource in the UI, and click the Dedicate
+button. |button to dedicate a zone, pod,cluster, or host|
+
+For implicit dedication: The administrator creates a compute service
+offering and in the Deployment Planner field, chooses
+ImplicitDedicationPlanner. Then in Planner Mode, the administrator
+specifies either Strict or Preferred, depending on whether it is
+permissible to allow some use of shared resources when dedicated
+resources are not available. Whenever a user creates a VM based on this
+service offering, it is allocated on one of the dedicated hosts.
+
+
+How to Use Dedicated Hosts
+~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+To use an explicitly dedicated host, use the explicit-dedicated type of
+affinity group (see `“Affinity Groups” <virtual_machines.html#affinity-groups>`_). 
+For example, when creating a new VM, an
+end user can choose to place it on dedicated infrastructure. This
+operation will succeed only if some infrastructure has already been
+assigned as dedicated to the user's account or domain.
+
+
+Behavior of Dedicated Hosts, Clusters, Pods, and Zones
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+The administrator can live migrate VMs away from dedicated hosts if
+desired, whether the destination is a host reserved for a different
+account/domain or a host that is shared (not dedicated to any particular
+account or domain). CloudStack will generate an alert, but the operation
+is allowed.
+
+Dedicated hosts can be used in conjunction with host tags. If both a
+host tag and dedication are requested, the VM will be placed only on a
+host that meets both requirements. If there is no dedicated resource
+available to that user that also has the host tag requested by the user,
+then the VM will not deploy.
+
+If you delete an account or domain, any hosts, clusters, pods, and zones
+that were dedicated to it are freed up. They will now be available to be
+shared by any account or domain, or the administrator may choose to
+re-dedicate them to a different account or domain.
+
+System VMs and virtual routers affect the behavior of host dedication.
+System VMs and virtual routers are owned by the CloudStack system
+account, and they can be deployed on any host. They do not adhere to
+explicit dedication. The presence of system vms and virtual routers on a
+host makes it unsuitable for strict implicit dedication. The host can
+not be used for strict implicit dedication, because the host already has
+VMs of a specific account (the default system account). However, a host
+with system VMs or virtual routers can be used for preferred implicit
+dedication.
+
+
+Using an LDAP Server for User Authentication
+--------------------------------------------
+
+You can use an external LDAP server such as Microsoft Active Directory
+or ApacheDS to authenticate CloudStack end-users. CloudStack will search
+the external LDAP directory tree starting at a specified base directory
+and gets user info such as first name, last name, email and username.
+
+To authenticate, username and password entered by the user are used.
+Cloudstack does a search for a user with the given username. If it
+exists, it does a bind request with DN and password.
+
+To set up LDAP authentication in CloudStack, call the CloudStack API
+command ``addLdapConfiguration`` and provide Hostname or IP address
+and listening port of the LDAP server. You could configure multiple
+servers as well. These are expected to be replicas. If one fails,
+the next one is used.
+
+The following global configurations should also be configured (the
+default values are for openldap)
+
+-  ``ldap.basedn``:	Sets the basedn for LDAP. Ex: **OU=APAC,DC=company,DC=com**
+
+-  ``ldap.bind.principal``, ``ldap.bind.password``: DN and password for a user
+   who can list all the users in the above basedn. Ex:
+   **CN=Administrator, OU=APAC, DC=company, DC=com**
+
+-  ``ldap.user.object``: object type of users within LDAP. Defaults value is
+   **user** for AD and **interorgperson** for openldap.
+
+-  ``ldap.email.attribute``: email attribute within ldap for a user. Default
+   value for AD and openldap is **mail**.
+
+-  ``ldap.firstname.attribute``: firstname attribute within ldap for a user.
+   Default value for AD and openldap is **givenname**.
+
+-  ``ldap.lastname.attribute``: lastname attribute within ldap for a user.
+   Default value for AD and openldap is **sn**.
+
+-  ``ldap.username.attribute``: username attribute for a user within LDAP.
+   Default value is **SAMAccountName** for AD and **uid** for openldap.
+
+
+Restricting LDAP users to a group:
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+-  ``ldap.search.group.principle``: this is optional and if set only users from
+   this group are listed.
+
+
+LDAP SSL:
+~~~~~~~~~
+
+If the LDAP server requires SSL, you need to enable the below configurations.
+Before enabling SSL for LDAP, you need to get the certificate which the LDAP server is using and add it to a trusted keystore.
+You will need to know the path to the keystore and the password.
+
+-  ``ldap.truststore`` : truststore path
+-  ``ldap.truststore.password`` : truststore password
+
+
+LDAP groups:
+~~~~~~~~~~~~
+
+-  ``ldap.group.object``: object type of groups within LDAP. Default value is
+   group for AD and **groupOfUniqueNames** for openldap.	
+
+-  ``ldap.group.user.uniquemember``: attribute for uniquemembers within a group.
+   Default value is **member** for AD and **uniquemember** for openldap.
+
+Once configured, on Add Account page, you will see an "Add LDAP Account" button
+which opens a dialog and the selected users can be imported.
+
+.. figure:: /_static/images/CloudStack-ldap-screen1.png
+   :align:   center
+
+
+You could also use api commands: ``listLdapUsers``, ``ldapCreateAccount`` and
+``importLdapUsers``.
+
+Once LDAP is enabled, the users will not be allowed to changed password
+directly in cloudstack.
+
+
+
+.. |button to dedicate a zone, pod,cluster, or host| image:: /_static/images/dedicate-resource-button.png
+
+Using a SAML 2.0 Identity Provider for User Authentication
+----------------------------------------------------------
+
+You can use a SAML 2.0 Identity Provider with CloudStack for user
+authentication. This will require enabling the SAML 2.0 service provider plugin
+in CloudStack. To do that first, enable the SAML plugin by setting
+``saml2.enabled`` to ``true`` and restart management server.
+
+Starting 4.5.2, the SAML plugin uses an authorization workflow where users should
+be authorized by an admin using ``authorizeSamlSso`` API before those users can
+use Single Sign On against a specific IDP. This can be done by ticking the enable
+SAML Single Sign On checkbox and selecting a IDP when adding or importing users.
+For existing users, admin can go to the user's page and click on configure
+SAML SSO option to enable/disable SSO for a user and select a Identity Provider.
+A user can be authorized to authenticate against only one IDP.
+
+The CloudStack service provider metadata is accessible using the
+``getSPMetadata`` API command, or from the URL
+http://acs-server:8080/client/api?command=getSPMetadata where acs-server is the
+domain name or IP address of the management server. The IDP administrator can
+get the SP metadata from CloudStack and add it to their IDP server.
+
+To start a SAML 2.0 Single Sign-On authentication, on the login page users need to
+select the Identity Provider or Institution/Department they can authenticate with
+and click on Login button. This action call the ``samlsso`` API command which
+will redirect the user to the Identity Provider's login page. Upon successful
+authentication, the IdP will redirect the user to CloudStack. In case a user has
+multiple user accounts with the same username (across domains) for the same
+authorized IDP, that user would need to specify domainpath after selecting their
+IDP server from the dropdown list. By default, users don't need to specify any
+domain path. After a user is successfully authenticated by an IDP server, the SAML
+authentication plugin finds user accounts whose username match the username
+attribute value returned by the SAML authentication response; it fails
+only when it finds that there are multiple user accounts with the same user name
+for the specific IDP otherwise the unique useraccount is allowed to proceed and
+the user is logged into their account.
+
+Limitations:
+
+- The plugin uses a user attribute returned by the IDP server in the SAML response
+  to find and map the authorized user in CloudStack. The default attribute is `uid`.
+
+- The SAML authentication plugin supports HTTP-Redirect and HTTP-Post bindings.
+
+- Tested with Shibboleth 2.4, SSOCircle, Microsoft ADFS, OneLogin, Feide OpenIDP,
+  PingIdentity.
+
+The following global configuration should be configured:
+
+- ``saml2.enabled``: Indicates whether SAML SSO plugin is enabled or not true. Default is **false**
+
+- ``saml2.sp.id``: SAML2 Service Provider Identifier string
+
+- ``saml2.idp.metadata.url``: SAML2 Identity Provider Metadata XML Url or Filename. If a URL is not provided, it will look for a file in the config directory /etc/cloudstack/management
+
+- ``saml2.default.idpid``: The default IdP entity ID to use only in case of multiple IdPs
+
+- ``saml2.sigalg``: The algorithm to use to when signing a SAML request. Default is SHA1, allowed algorithms: SHA1, SHA256, SHA384, SHA512.
+
+- ``saml2.redirect.url``: The CloudStack UI url the SSO should redirected to when successful. Default is **http://localhost:8080/client**
+
+- ``saml2.sp.org.name``: SAML2 Service Provider Organization Name
+
+- ``saml2.sp.org.url``: SAML2 Service Provider Organization URL
+
+- ``saml2.sp.contact.email``: SAML2 Service Provider Contact Email Address
+
+- ``saml2.sp.contact.person``: SAML2 Service Provider Contact Person Name
+
+- ``saml2.sp.slo.url``: SAML2 CloudStack Service Provider Single Log Out URL
+
+- ``saml2.sp.sso.url``: SAML2 CloudStack Service Provider Single Sign On URL
+
+- ``saml2.user.attribute``: Attribute name to be looked for in SAML response that will contain the username. Default is **uid**
+
+- ``saml2.timeout``: SAML2 IDP Metadata refresh interval in seconds, minimum value is set to 300. Default is 1800
+
diff --git a/source/adminguide/administration.rst b/source/adminguide/administration.rst
new file mode 100644
index 0000000..4baa17f
--- /dev/null
+++ b/source/adminguide/administration.rst
@@ -0,0 +1,77 @@
+.. Licensed to the Apache Software Foundation (ASF) under one
+   or more contributor license agreements.  See the NOTICE file
+   distributed with this work for additional information#
+   regarding copyright ownership.  The ASF licenses this file
+   to you under the Apache License, Version 2.0 (the
+   "License"); you may not use this file except in compliance
+   with the License.  You may obtain a copy of the License at
+   http://www.apache.org/licenses/LICENSE-2.0
+   Unless required by applicable law or agreed to in writing,
+   software distributed under the License is distributed on an
+   "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+   KIND, either express or implied.  See the License for the
+   specific language governing permissions and limitations
+   under the License.
+
+
+User Services
+=============
+
+In addition to the physical and logical infrastructure of your cloud and
+the CloudStack software and servers, you also need a layer of user
+services so that people can actually make use of the cloud. This means
+not just a user UI, but a set of options and resources that users can
+choose from, such as templates for creating virtual machines, disk
+storage, and more. If you are running a commercial service, you will be
+keeping track of what services and resources users are consuming and
+charging them for that usage. Even if you do not charge anything for
+people to use your cloud – say, if the users are strictly internal to
+your organization, or just friends who are sharing your cloud – you can
+still keep track of what services they use and how much of them.
+
+
+Service Offerings, Disk Offerings, Network Offerings, and Templates
+-------------------------------------------------------------------
+
+A user creating a new instance can make a variety of choices about its
+characteristics and capabilities. CloudStack provides several ways to
+present users with choices when creating a new instance:
+
+-  Service Offerings, defined by the CloudStack administrator, provide a
+   choice of CPU speed, number of CPUs, RAM size, tags on the root disk,
+   and other choices. See Creating a New Compute Offering.
+
+-  Disk Offerings, defined by the CloudStack administrator, provide a
+   choice of disk size and IOPS (Quality of Service) for primary data
+   storage. See Creating a New Disk Offering.
+
+-  Network Offerings, defined by the CloudStack administrator, describe
+   the feature set that is available to end users from the virtual
+   router or external networking devices on a given guest network. See
+   Network Offerings.
+
+-  Templates, defined by the CloudStack administrator or by any
+   CloudStack user, are the base OS images that the user can choose from
+   when creating a new instance. For example, CloudStack includes CentOS
+   as a template. See Working with Templates.
+
+In addition to these choices that are provided for users, there is
+another type of service offering which is available only to the
+CloudStack root administrator, and is used for configuring virtual
+infrastructure resources. For more information, see Upgrading a Virtual
+Router with System Service Offerings.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
diff --git a/source/adminguide/api.rst b/source/adminguide/api.rst
new file mode 100644
index 0000000..19ad8da
--- /dev/null
+++ b/source/adminguide/api.rst
@@ -0,0 +1,90 @@
+.. Licensed to the Apache Software Foundation (ASF) under one
+   or more contributor license agreements.  See the NOTICE file
+   distributed with this work for additional information#
+   regarding copyright ownership.  The ASF licenses this file
+   to you under the Apache License, Version 2.0 (the
+   "License"); you may not use this file except in compliance
+   with the License.  You may obtain a copy of the License at
+   http://www.apache.org/licenses/LICENSE-2.0
+   Unless required by applicable law or agreed to in writing,
+   software distributed under the License is distributed on an
+   "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+   KIND, either express or implied.  See the License for the
+   specific language governing permissions and limitations
+   under the License.
+ 
+
+The CloudStack API is a low level API that has been used to implement
+the CloudStack web UIs. It is also a good basis for implementing other
+popular APIs such as EC2/S3 and emerging DMTF standards.
+
+Many CloudStack API calls are asynchronous. These will return a Job ID
+immediately when called. This Job ID can be used to query the status of
+the job later. Also, status calls on impacted resources will provide
+some indication of their state.
+
+The API has a REST-like query basis and returns results in XML or JSON.
+
+See `the Developer’s Guide <https://cwiki.apache.org/confluence/display/CLOUDSTACK/Development+101>`_
+and `the API Reference <http://cloudstack.apache.org/docs/api/>`_.
+
+
+Provisioning and Authentication API
+-----------------------------------
+
+CloudStack expects that a customer will have their own user provisioning
+infrastructure. It provides APIs to integrate with these existing
+systems where the systems call out to CloudStack to add/remove users..
+
+CloudStack supports pluggable authenticators. By default, CloudStack
+assumes it is provisioned with the user’s password, and as a result
+authentication is done locally. However, external authentication is
+possible as well. For example, see Using an LDAP Server for User
+Authentication.
+
+
+User Data and Meta Data
+-----------------------
+
+CloudStack provides API access to attach up to 32KB of user data to a
+deployed VM. Deployed VMs also have access to instance metadata via the
+virtual router.
+
+User data can be accessed once the IP address of the virtual router is
+known. Once the IP address is known, use the following steps to access
+the user data:
+
+#. Run the following command to find the virtual router.
+
+   .. code:: bash
+
+      # cat /var/lib/dhclient/dhclient-eth0.leases | grep dhcp-server-identifier | tail -1
+
+#. Access user data by running the following command using the result of
+   the above command
+
+   .. code:: bash
+
+      # curl http://10.1.1.1/latest/user-data
+
+Meta Data can be accessed similarly, using a URL of the form
+http://10.1.1.1/latest/meta-data/{metadata type}. (For backwards
+compatibility, the previous URL http://10.1.1.1/latest/{metadata type}
+is also supported.) For metadata type, use one of the following:
+
+-  service-offering. A description of the VMs service offering
+
+-  availability-zone. The Zone name
+
+-  local-ipv4. The guest IP of the VM
+
+-  local-hostname. The hostname of the VM
+
+-  public-ipv4. The first public IP for the router. (E.g. the first IP
+   of eth2)
+
+-  public-hostname. This is the same as public-ipv4
+
+-  instance-id. The instance name of the VM
+
+
diff --git a/source/adminguide/autoscale_without_netscaler.rst b/source/adminguide/autoscale_without_netscaler.rst
new file mode 100644
index 0000000..e2f5799
--- /dev/null
+++ b/source/adminguide/autoscale_without_netscaler.rst
@@ -0,0 +1,177 @@
+.. Licensed to the Apache Software Foundation (ASF) under one
+   or more contributor license agreements.  See the NOTICE file
+   distributed with this work for additional information#
+   regarding copyright ownership.  The ASF licenses this file
+   to you under the Apache License, Version 2.0 (the
+   "License"); you may not use this file except in compliance
+   with the License.  You may obtain a copy of the License at
+   http://www.apache.org/licenses/LICENSE-2.0
+   Unless required by applicable law or agreed to in writing,
+   software distributed under the License is distributed on an
+   "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+   KIND, either express or implied.  See the License for the
+   specific language governing permissions and limitations
+   under the License.
+
+
+Configuring AutoScale without using NetScaler
+=============================================
+
+.. warning:: 
+   This feature is currently only available on the master branch and will be 
+   released in the 4.4 release.
+
+
+What is AutoScaling?
+--------------------
+
+AutoScaling allows you to scale your back-end services or application VMs up 
+or down seamlessly and automatically according to the conditions you define. 
+With AutoScaling enabled, you can ensure that the number of VMs you are using 
+seamlessly scale up when demand increases, and automatically decreases when 
+demand subsides. Thus it helps you save compute costs by terminating underused 
+VMs automatically and launching new VMs when you need them, without the need 
+for manual intervention.
+
+
+Hypervisor support
+------------------
+
+At that time, AutoScaling without NetScaler only supports for Xenserver. We 
+are working to support KVM also.
+
+
+Prerequisites
+-------------
+
+Before you configure an AutoScale rule, consider the following:
+
+-  Ensure that the necessary template is prepared before configuring AutoScale. 
+   Firstly you must install the PV-driver, which helps Xenserver collect 
+   performance parameters (CPU and memory) into VMs. Beside, When a VM is 
+   deployed by using a template and when it comes up, the application should be 
+   up and running.
+
+
+Configuration
+-------------
+
+Specify the following:
+
+.. image:: /_static/images/autoscale-config.png
+
+-  Template: A template consists of a base OS image and application. A 
+   template is used to provision the new instance of an application on a 
+   scaleup action. When a VM is deployed from a template, the VM can start 
+   taking the traffic from the load balancer without any admin intervention. 
+   For example, if the VM is deployed for a Web service, it should have the 
+   Web server running, the database connected, and so on.
+
+-  Compute offering: A predefined set of virtual hardware attributes, 
+   including CPU speed, number of CPUs, and RAM size, that the user can select 
+   when creating a new virtual machine instance. Choose one of the compute 
+   offerings to be used while provisioning a VM instance as part of scaleup 
+   action.
+
+-  Min Instance: The minimum number of active VM instances that is assigned to 
+   a load balancing rule. The active VM instances are the application 
+   instances that are up and serving the traffic, and are being load balanced. 
+   This parameter ensures that a load balancing rule has at least the 
+   configured number of active VM instances are available to serve the traffic.
+
+-  Max Instance: Maximum number of active VM instances that should be assigned 
+   to a load balancing rule. This parameter defines the upper limit of active 
+   VM instances that can be assigned to a load balancing rule.
+
+   Specifying a large value for the maximum instance parameter might result in 
+   provisioning large number of VM instances, which in turn leads to a single 
+   load balancing rule exhausting the VM instances limit specified at the 
+   account or domain level.
+
+Specify the following scale-up and scale-down policies:
+
+-  Duration: The duration, in seconds, for which the conditions you specify 
+   must be true to trigger a scaleup action. The conditions defined should 
+   hold true for the entire duration you specify for an AutoScale action to be 
+   invoked.
+
+-  Counter: The performance counters expose the state of the monitored 
+   instances. We added two new counter to work with that feature:
+
+   -  Linux User CPU [native] - percentage
+   -  Linux User RAM [native] - percentage
+
+   Remember to choose one of them. If you choose anything else, the 
+   autoscaling will not work.
+
+-  Operator: The following five relational operators are supported in 
+   AutoScale feature: Greater than, Less than, Less than or equal to, Greater 
+   than or equal to, and Equal to.
+
+-  Threshold: Threshold value to be used for the counter. Once the counter 
+   defined above breaches the threshold value, the AutoScale feature initiates 
+   a scaleup or scaledown action.
+
+-  Add: Click Add to add the condition.
+
+   Additionally, if you want to configure the advanced settings, click Show 
+   advanced settings, and specify the following:
+
+-  Polling interval: Frequency in which the conditions, combination of counter, 
+   operator and threshold, are to be evaluated before taking a scale up or 
+   down action. The default polling interval is 30 seconds.
+
+-  Quiet Time: This is the cool down period after an AutoScale action is 
+   initiated. The time includes the time taken to complete provisioning a VM 
+   instance from its template and the time taken by an application to be ready 
+   to serve traffic. This quiet time allows the fleet to come up to a stable 
+   state before any action can take place. The default is 300 seconds.
+
+-  Destroy VM Grace Period: The duration in seconds, after a scaledown action 
+   is initiated, to wait before the VM is destroyed as part of scaledown 
+   action. This is to ensure graceful close of any pending sessions or 
+   transactions being served by the VM marked for destroy. The default is 120 
+   seconds.
+
+-  Apply: Click Apply to create the AutoScale configuration.
+
+
+Disabling and Enabling an AutoScale Configuration
+-------------------------------------------------
+
+If you want to perform any maintenance operation on the AutoScale VM instances, 
+disable the AutoScale configuration. When the AutoScale configuration is 
+disabled, no scaleup or scaledown action is performed. You can use this 
+downtime for the maintenance activities. To disable the AutoScale 
+configuration, click the Disable AutoScale button.
+
+The button toggles between enable and disable, depending on whether AutoScale 
+is currently enabled or not. After the maintenance operations are done, you 
+can enable the AutoScale configuration back. To enable, open the AutoScale 
+configuration page again, then click the Enable AutoScale button.
+
+
+Updating an AutoScale Configuration
+-----------------------------------
+
+You can update the various parameters and add or delete the conditions in a 
+scaleup or scaledown rule. Before you update an AutoScale configuration, 
+ensure that you disable the AutoScale load balancer rule by clicking the 
+Disable AutoScale button.
+
+After you modify the required AutoScale parameters, click Apply. To apply the 
+new AutoScale policies, open the AutoScale configuration page again, then 
+click the Enable AutoScale button.
+
+
+Runtime Considerations
+----------------------
+
+An administrator should not assign a VM to a load balancing rule which is 
+configured for AutoScale.
+
+Making API calls outside the context of AutoScale, such as destroyVM, on an 
+autoscaled VM leaves the load balancing configuration in an inconsistent state. 
+Though VM is destroyed from the load balancer rule, it continues be showed as 
+a service assigned to a rule inside the context of AutoScale.
+
diff --git a/source/adminguide/events.rst b/source/adminguide/events.rst
new file mode 100644
index 0000000..629fcc4
--- /dev/null
+++ b/source/adminguide/events.rst
@@ -0,0 +1,368 @@
+.. Licensed to the Apache Software Foundation (ASF) under one
+   or more contributor license agreements.  See the NOTICE file
+   distributed with this work for additional information#
+   regarding copyright ownership.  The ASF licenses this file
+   to you under the Apache License, Version 2.0 (the
+   "License"); you may not use this file except in compliance
+   with the License.  You may obtain a copy of the License at
+   http://www.apache.org/licenses/LICENSE-2.0
+   Unless required by applicable law or agreed to in writing,
+   software distributed under the License is distributed on an
+   "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+   KIND, either express or implied.  See the License for the
+   specific language governing permissions and limitations
+   under the License.
+   
+
+Event Notification
+==================
+
+An event is essentially a significant or meaningful change in the state
+of both virtual and physical resources associated with a cloud
+environment. Events are used by monitoring systems, usage and billing
+systems, or any other event-driven workflow systems to discern a pattern
+and make the right business decision. In CloudStack an event could be a
+state change of virtual or physical resources, an action performed by an
+user (action events), or policy based events (alerts).
+
+
+Event Logs
+----------
+
+There are two types of events logged in the CloudStack Event Log.
+Standard events log the success or failure of an event and can be used
+to identify jobs or processes that have failed. There are also long
+running job events. Events for asynchronous jobs log when a job is
+scheduled, when it starts, and when it completes. Other long running
+synchronous jobs log when a job starts, and when it completes. Long
+running synchronous and asynchronous event logs can be used to gain more
+information on the status of a pending job or can be used to identify a
+job that is hanging or has not started. The following sections provide
+more information on these events..
+
+
+Notification
+------------
+
+Event notification framework provides a means for the Management Server
+components to publish and subscribe to CloudStack events. Event
+notification is achieved by implementing the concept of event bus
+abstraction in the Management Server.
+
+A new event for state change, resource state change, is introduced as
+part of Event notification framework. Every resource, such as user VM,
+volume, NIC, network, public IP, snapshot, and template, is associated
+with a state machine and generates events as part of the state change.
+That implies that a change in the state of a resource results in a state
+change event, and the event is published in the corresponding state
+machine on the event bus. All the CloudStack events (alerts, action
+events, usage events) and the additional category of resource state
+change events, are published on to the events bus.
+
+Implementations
+~~~~~~~~~~~~~~~
+An event bus is introduced in the
+Management Server that allows the CloudStack components and extension
+plug-ins to subscribe to the events by using the Advanced Message
+Queuing Protocol (AMQP) client. In CloudStack, a default implementation
+of event bus is provided as a plug-in that uses the RabbitMQ AMQP
+client. The AMQP client pushes the published events to a compatible AMQP
+server. Therefore all the CloudStack events are published to an exchange
+in the AMQP server.
+
+Additionally, both an in-memory implementation and an Apache Kafka
+implementation are also available.
+
+Use Cases
+~~~~~~~~~
+
+The following are some of the use cases:
+
+-  Usage or Billing Engines: A third-party cloud usage solution can
+   implement a plug-in that can connects to CloudStack to subscribe to
+   CloudStack events and generate usage data. The usage data is consumed
+   by their usage software.
+
+-  AMQP plug-in can place all the events on the a message queue, then a
+   AMQP message broker can provide topic-based notification to the
+   subscribers.
+
+-  Publish and Subscribe notification service can be implemented as a
+   pluggable service in CloudStack that can provide rich set of APIs for
+   event notification, such as topics-based subscription and
+   notification. Additionally, the pluggable service can deal with
+   multi-tenancy, authentication, and authorization issues.
+
+
+AMQP Configuration
+~~~~~~~~~~~~~~~~~~~
+
+As a CloudStack administrator, perform the following one-time
+configuration to enable event notification framework. At run time no
+changes can control the behaviour.
+
+#. Create the folder ``/etc/cloudstack/management/META-INF/cloudstack/core``
+
+#. Inside that folder, open ``spring-event-bus-context.xml``.
+
+#. Define a bean named ``eventNotificationBus`` as follows:
+
+   -  name : Specify a name for the bean.
+
+   -  server : The name or the IP address of the RabbitMQ AMQP server.
+
+   -  port : The port on which RabbitMQ server is running.
+
+   -  username : The username associated with the account to access the
+      RabbitMQ server.
+
+   -  password : The password associated with the username of the
+      account to access the RabbitMQ server.
+
+   -  exchange : The exchange name on the RabbitMQ server where
+      CloudStack events are published.
+
+      A sample bean is given below:
+
+      .. code:: bash
+
+         <beans xmlns="http://www.springframework.org/schema/beans"
+         xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
+         xmlns:context="http://www.springframework.org/schema/context"
+         xmlns:aop="http://www.springframework.org/schema/aop"
+         xsi:schemaLocation="http://www.springframework.org/schema/beans
+         http://www.springframework.org/schema/beans/spring-beans-3.0.xsd
+         http://www.springframework.org/schema/aop http://www.springframework.org/schema/aop/spring-aop-3.0.xsd
+         http://www.springframework.org/schema/context
+         http://www.springframework.org/schema/context/spring-context-3.0.xsd">
+            <bean id="eventNotificationBus" class="org.apache.cloudstack.mom.rabbitmq.RabbitMQEventBus">
+               <property name="name" value="eventNotificationBus"/>
+               <property name="server" value="127.0.0.1"/>
+               <property name="port" value="5672"/>
+               <property name="username" value="guest"/>
+               <property name="password" value="guest"/>
+               <property name="exchange" value="cloudstack-events"/>
+            </bean>
+         </beans>
+
+      The ``eventNotificationBus`` bean represents the
+      ``org.apache.cloudstack.mom.rabbitmq.RabbitMQEventBus`` class.
+      
+      If you want to use encrypted values for the username and password, you have to include a bean to pass those
+      as variables from a credentials file.
+
+      A sample is given below
+
+      .. code:: bash
+
+         <beans xmlns="http://www.springframework.org/schema/beans"
+                xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
+                xmlns:context="http://www.springframework.org/schema/context"
+                xmlns:aop="http://www.springframework.org/schema/aop"
+                xsi:schemaLocation="http://www.springframework.org/schema/beans
+                 http://www.springframework.org/schema/beans/spring-beans-3.0.xsd
+                 http://www.springframework.org/schema/aop http://www.springframework.org/schema/aop/spring-aop-3.0.xsd
+                 http://www.springframework.org/schema/context
+                 http://www.springframework.org/schema/context/spring-context-3.0.xsd"
+         >
+
+            <bean id="eventNotificationBus" class="org.apache.cloudstack.mom.rabbitmq.RabbitMQEventBus">
+               <property name="name" value="eventNotificationBus"/>
+               <property name="server" value="127.0.0.1"/>
+               <property name="port" value="5672"/>
+               <property name="username" value="${username}"/>
+               <property name="password" value="${password}"/>
+               <property name="exchange" value="cloudstack-events"/>
+            </bean>
+
+            <bean id="environmentVariablesConfiguration" class="org.jasypt.encryption.pbe.config.EnvironmentStringPBEConfig">
+               <property name="algorithm" value="PBEWithMD5AndDES" />
+               <property name="passwordEnvName" value="APP_ENCRYPTION_PASSWORD" />
+            </bean>
+
+            <bean id="configurationEncryptor" class="org.jasypt.encryption.pbe.StandardPBEStringEncryptor">
+               <property name="config" ref="environmentVariablesConfiguration" />
+            </bean>
+
+            <bean id="propertyConfigurer" class="org.jasypt.spring3.properties.EncryptablePropertyPlaceholderConfigurer">
+               <constructor-arg ref="configurationEncryptor" />
+               <property name="location" value="classpath:/cred.properties" />
+            </bean>
+         </beans>
+
+
+      Create a new file in the same folder called ``cred.properties`` and the specify the values for username and password as jascrypt encrypted strings
+
+      Sample, with ``guest`` as values for both fields:
+
+      .. code:: bash
+
+         username=nh2XrM7jWHMG4VQK18iiBQ==
+         password=nh2XrM7jWHMG4VQK18iiBQ==
+
+
+#. Restart the Management Server.
+
+Kafka Configuration
+~~~~~~~~~~~~~~~~~~~
+
+As a CloudStack administrator, perform the following one-time
+configuration to enable event notification framework. At run time no
+changes can control the behaviour.
+
+#. Create an appropriate configuration file in ``/etc/cloudstack/management/kafka.producer.properties``
+   which contains valid kafka configuration properties as documented in http://kafka.apache.org/documentation.html#newproducerconfigs
+   The properties may contain an additional ``topic`` property which if not provided will default to ``cloudstack``.
+   While ``key.serializer`` and ``value.serializer`` are usually required for a producer to correctly start, they may be omitted and
+   will default to ``org.apache.kafka.common.serialization.StringSerializer``.
+
+#. Create the folder ``/etc/cloudstack/management/META-INF/cloudstack/core``
+
+#. Inside that folder, open ``spring-event-bus-context.xml``.
+
+#. Define a bean named ``eventNotificationBus`` with a single ``name`` attribute, A sample bean is given below:
+
+   .. code:: xml
+
+       <beans xmlns="http://www.springframework.org/schema/beans"
+              xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
+              xmlns:context="http://www.springframework.org/schema/context"
+              xmlns:aop="http://www.springframework.org/schema/aop"
+              xsi:schemaLocation="http://www.springframework.org/schema/beans
+                                  http://www.springframework.org/schema/beans/spring-beans-3.0.xsd
+                                  http://www.springframework.org/schema/aop http://www.springframework.org/schema/aop/spring-aop-3.0.xsd
+                                  http://www.springframework.org/schema/context
+                                  http://www.springframework.org/schema/context/spring-context-3.0.xsd">
+          <bean id="eventNotificationBus" class="org.apache.cloudstack.mom.kafka.KafkaEventBus">
+            <property name="name" value="eventNotificationBus"/>
+          </bean>
+        </beans>
+
+#. Restart the Management Server.
+
+
+Standard Events
+---------------
+
+The events log records three types of standard events.
+
+-  INFO. This event is generated when an operation has been successfully
+   performed.
+
+-  WARN. This event is generated in the following circumstances.
+
+   -  When a network is disconnected while monitoring a template
+      download.
+
+   -  When a template download is abandoned.
+
+   -  When an issue on the storage server causes the volumes to fail
+      over to the mirror storage server.
+
+-  ERROR. This event is generated when an operation has not been
+   successfully performed
+
+
+Long Running Job Events
+-----------------------
+
+The events log records three types of standard events.
+
+-  INFO. This event is generated when an operation has been successfully
+   performed.
+
+-  WARN. This event is generated in the following circumstances.
+
+   -  When a network is disconnected while monitoring a template
+      download.
+
+   -  When a template download is abandoned.
+
+   -  When an issue on the storage server causes the volumes to fail
+      over to the mirror storage server.
+
+-  ERROR. This event is generated when an operation has not been
+   successfully performed
+
+
+Event Log Queries
+-----------------
+
+Database logs can be queried from the user interface. The list of events
+captured by the system includes:
+
+-  Virtual machine creation, deletion, and on-going management
+   operations
+
+-  Virtual router creation, deletion, and on-going management operations
+
+-  Template creation and deletion
+
+-  Network/load balancer rules creation and deletion
+
+-  Storage volume creation and deletion
+
+-  User login and logout
+
+
+Deleting and Archiving Events and Alerts
+----------------------------------------
+
+CloudStack provides you the ability to delete or archive the existing
+alerts and events that you no longer want to implement. You can
+regularly delete or archive any alerts or events that you cannot, or do
+not want to resolve from the database.
+
+You can delete or archive individual alerts or events either directly by
+using the Quickview or by using the Details page. If you want to delete
+multiple alerts or events at the same time, you can use the respective
+context menu. You can delete alerts or events by category for a time
+period. For example, you can select categories such as **USER.LOGOUT**,
+**VM.DESTROY**, **VM.AG.UPDATE**, **CONFIGURATION.VALUE.EDI**, and so
+on. You can also view the number of events or alerts archived or
+deleted.
+
+In order to support the delete or archive alerts, the following global
+parameters have been added:
+
+-  **alert.purge.delay**: The alerts older than specified number of days
+   are purged. Set the value to 0 to never purge alerts automatically.
+
+-  **alert.purge.interval**: The interval in seconds to wait before
+   running the alert purge thread. The default is 86400 seconds (one
+   day).
+
+.. note:: 
+   Archived alerts or events cannot be viewed in the UI or by using the
+   API. They are maintained in the database for auditing or compliance
+   purposes.
+
+
+Permissions
+~~~~~~~~~~~
+
+Consider the following:
+
+-  The root admin can delete or archive one or multiple alerts or
+   events.
+
+-  The domain admin or end user can delete or archive one or multiple
+   events.
+
+
+Procedure
+~~~~~~~~~
+
+#. Log in as administrator to the CloudStack UI.
+
+#. In the left navigation, click Events.
+
+#. Perform either of the following:
+
+   -  To archive events, click Archive Events, and specify event type
+      and date.
+
+   -  To archive events, click Delete Events, and specify event type and
+      date.
+
+#. Click OK.
diff --git a/source/adminguide/hosts.rst b/source/adminguide/hosts.rst
new file mode 100644
index 0000000..71b55d7
--- /dev/null
+++ b/source/adminguide/hosts.rst
@@ -0,0 +1,747 @@
+.. Licensed to the Apache Software Foundation (ASF) under one
+   or more contributor license agreements.  See the NOTICE file
+   distributed with this work for additional information#
+   regarding copyright ownership.  The ASF licenses this file
+   to you under the Apache License, Version 2.0 (the
+   "License"); you may not use this file except in compliance
+   with the License.  You may obtain a copy of the License at
+   http://www.apache.org/licenses/LICENSE-2.0
+   Unless required by applicable law or agreed to in writing,
+   software distributed under the License is distributed on an
+   "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+   KIND, either express or implied.  See the License for the
+   specific language governing permissions and limitations
+   under the License.
+
+
+Adding Hosts
+------------
+
+Additional hosts can be added at any time to provide more capacity for
+guest VMs. For requirements and instructions, see :ref:`adding-a-host`.
+
+
+Scheduled Maintenance and Maintenance Mode for Hosts
+----------------------------------------------------
+
+You can place a host into maintenance mode. When maintenance mode is
+activated, the host becomes unavailable to receive new guest VMs, and
+the guest VMs already running on the host are seamlessly migrated to
+another host not in maintenance mode. This migration uses live migration
+technology and does not interrupt the execution of the guest.
+
+
+vCenter and Maintenance Mode
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+To enter maintenance mode on a vCenter host, both vCenter and CloudStack
+must be used in concert. CloudStack and vCenter have separate
+maintenance modes that work closely together.
+
+#. Place the host into CloudStack's "scheduled maintenance" mode. This
+   does not invoke the vCenter maintenance mode, but only causes VMs to
+   be migrated off the host
+
+   When the CloudStack maintenance mode is requested, the host first
+   moves into the Prepare for Maintenance state. In this state it cannot
+   be the target of new guest VM starts. Then all VMs will be migrated
+   off the server. Live migration will be used to move VMs off the host.
+   This allows the guests to be migrated to other hosts with no
+   disruption to the guests. After this migration is completed, the host
+   will enter the Ready for Maintenance mode.
+
+#. Wait for the "Ready for Maintenance" indicator to appear in the UI.
+
+#. Now use vCenter to perform whatever actions are necessary to maintain
+   the host. During this time, the host cannot be the target of new VM
+   allocations.
+
+#. When the maintenance tasks are complete, take the host out of
+   maintenance mode as follows:
+
+   #. First use vCenter to exit the vCenter maintenance mode.
+
+      This makes the host ready for CloudStack to reactivate it.
+
+   #. Then use CloudStack's administrator UI to cancel the CloudStack
+      maintenance mode
+
+      When the host comes back online, the VMs that were migrated off of
+      it may be migrated back to it manually and new VMs can be added.
+
+
+XenServer and Maintenance Mode
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+For XenServer, you can take a server offline temporarily by using the
+Maintenance Mode feature in XenCenter. When you place a server into
+Maintenance Mode, all running VMs are automatically migrated from it to
+another host in the same pool. If the server is the pool master, a new
+master will also be selected for the pool. While a server is Maintenance
+Mode, you cannot create or start any VMs on it.
+
+**To place a server in Maintenance Mode:**
+
+#. In the Resources pane, select the server, then do one of the
+   following:
+
+   -  Right-click, then click Enter Maintenance Mode on the shortcut
+      menu.
+
+   -  On the Server menu, click Enter Maintenance Mode.
+
+#. Click Enter Maintenance Mode.
+
+The server's status in the Resources pane shows when all running VMs
+have been successfully migrated off the server.
+
+**To take a server out of Maintenance Mode:**
+
+#. In the Resources pane, select the server, then do one of the
+   following:
+
+   -  Right-click, then click Exit Maintenance Mode on the shortcut
+      menu.
+
+   -  On the Server menu, click Exit Maintenance Mode.
+
+#. Click Exit Maintenance Mode.
+
+
+Disabling and Enabling Zones, Pods, and Clusters
+------------------------------------------------
+
+You can enable or disable a zone, pod, or cluster without permanently
+removing it from the cloud. This is useful for maintenance or when there
+are problems that make a portion of the cloud infrastructure unreliable.
+No new allocations will be made to a disabled zone, pod, or cluster
+until its state is returned to Enabled. When a zone, pod, or cluster is
+first added to the cloud, it is Disabled by default.
+
+To disable and enable a zone, pod, or cluster:
+
+#. Log in to the CloudStack UI as administrator
+
+#. In the left navigation bar, click Infrastructure.
+
+#. In Zones, click View More.
+
+#. If you are disabling or enabling a zone, find the name of the zone in
+   the list, and click the Enable/Disable button. |enable-disable.png|
+
+#. If you are disabling or enabling a pod or cluster, click the name of
+   the zone that contains the pod or cluster.
+
+#. Click the Compute tab.
+
+#. In the Pods or Clusters node of the diagram, click View All.
+
+#. Click the pod or cluster name in the list.
+
+#. Click the Enable/Disable button. |enable-disable.png|
+
+
+Removing Hosts
+--------------
+
+Hosts can be removed from the cloud as needed. The procedure to remove a
+host depends on the hypervisor type.
+
+
+Removing XenServer and KVM Hosts
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+A node cannot be removed from a cluster until it has been placed in
+maintenance mode. This will ensure that all of the VMs on it have been
+migrated to other Hosts. To remove a Host from the cloud:
+
+#. Place the node in maintenance mode.
+
+   See `“Scheduled Maintenance and Maintenance Mode for
+   Hosts” <#scheduled-maintenance-and-maintenance-mode-for-hosts>`_.
+
+#. For KVM, stop the cloud-agent service.
+
+#. Use the UI option to remove the node.
+
+   Then you may power down the Host, re-use its IP address, re-install
+   it, etc
+
+
+Removing vSphere Hosts
+~~~~~~~~~~~~~~~~~~~~~~
+
+To remove this type of host, first place it in maintenance mode, as
+described in `“Scheduled Maintenance and Maintenance Mode
+for Hosts” <#scheduled-maintenance-and-maintenance-mode-for-hosts>`_. Then use
+CloudStack to remove the host. CloudStack will not direct commands to a
+host that has been removed using CloudStack. However, the host may still
+exist in the vCenter cluster.
+
+
+Re-Installing Hosts
+-------------------
+
+You can re-install a host after placing it in maintenance mode and then
+removing it. If a host is down and cannot be placed in maintenance mode,
+it should still be removed before the re-install.
+
+
+Maintaining Hypervisors on Hosts
+--------------------------------
+
+When running hypervisor software on hosts, be sure all the hotfixes
+provided by the hypervisor vendor are applied. Track the release of
+hypervisor patches through your hypervisor vendor’s support channel, and
+apply patches as soon as possible after they are released. CloudStack
+will not track or notify you of required hypervisor patches. It is
+essential that your hosts are completely up to date with the provided
+hypervisor patches. The hypervisor vendor is likely to refuse to support
+any system that is not up to date with patches.
+
+.. note:: 
+   The lack of up-do-date hotfixes can lead to data corruption and lost VMs.
+
+(XenServer) For more information, see 
+`Highly Recommended Hotfixes for XenServer in the CloudStack Knowledge Base 
+<http://docs.cloudstack.org/Knowledge_Base/Possible_VM_corruption_if_XenServer_Hotfix_is_not_Applied/Highly_Recommended_Hotfixes_for_XenServer_5.6_SP2>`_.
+
+
+Changing Host Password
+----------------------
+
+The password for a XenServer Node, KVM Node, or vSphere Node may be
+changed in the database. Note that all Nodes in a Cluster must have the
+same password.
+
+To change a Node's password:
+
+#. Identify all hosts in the cluster.
+
+#. Change the password on all hosts in the cluster. Now the password for
+   the host and the password known to CloudStack will not match.
+   Operations on the cluster will fail until the two passwords match.
+
+#. if the password in the database is encrypted, it is (likely) necessary to
+   encrypt the new password using the database key before adding it to the database.
+
+   .. code:: bash
+
+      java -classpath /usr/share/cloudstack-common/lib/jasypt-1.9.0.jar \
+      org.jasypt.intf.cli.JasyptPBEStringEncryptionCLI \
+      encrypt.sh input="newrootpassword" \
+      password="databasekey" \
+      verbose=false
+
+#. Get the list of host IDs for the host in the cluster where you are
+   changing the password. You will need to access the database to
+   determine these host IDs. For each hostname "h" (or vSphere cluster)
+   that you are changing the password for, execute:
+
+   .. code:: bash
+
+      mysql> SELECT id FROM cloud.host WHERE name like '%h%';
+
+#. This should return a single ID. Record the set of such IDs for these
+   hosts. Now retrieve the host_details row id for the host
+
+   .. code:: bash
+
+      mysql> SELECT * FROM cloud.host_details WHERE name='password' AND host_id={previous step ID}; 
+
+#. Update the passwords for the host in the database. In this example,
+   we change the passwords for hosts with host IDs 5 and 12 and host_details IDs 8 and 22 to
+   "password".
+
+   .. code:: bash
+
+      mysql> UPDATE cloud.host_details SET value='password' WHERE id=8 OR id=22;
+
+
+Over-Provisioning and Service Offering Limits
+---------------------------------------------
+
+(Supported for XenServer, KVM, and VMware)
+
+CPU and memory (RAM) over-provisioning factors can be set for each
+cluster to change the number of VMs that can run on each host in the
+cluster. This helps optimize the use of resources. By increasing the
+over-provisioning ratio, more resource capacity will be used. If the
+ratio is set to 1, no over-provisioning is done.
+
+The administrator can also set global default over-provisioning ratios
+in the cpu.overprovisioning.factor and mem.overprovisioning.factor
+global configuration variables. The default value of these variables is
+1: over-provisioning is turned off by default.
+
+Over-provisioning ratios are dynamically substituted in CloudStack's
+capacity calculations. For example:
+
+Capacity = 2 GB
+Over-provisioning factor = 2
+Capacity after over-provisioning = 4 GB
+
+With this configuration, suppose you deploy 3 VMs of 1 GB each:
+
+Used = 3 GB
+Free = 1 GB
+
+The administrator can specify a memory over-provisioning ratio, and can
+specify both CPU and memory over-provisioning ratios on a per-cluster
+basis.
+
+In any given cloud, the optimum number of VMs for each host is affected
+by such things as the hypervisor, storage, and hardware configuration.
+These may be different for each cluster in the same cloud. A single
+global over-provisioning setting can not provide the best utilization
+for all the different clusters in the cloud. It has to be set for the
+lowest common denominator. The per-cluster setting provides a finer
+granularity for better utilization of resources, no matter where the
+CloudStack placement algorithm decides to place a VM.
+
+The overprovisioning settings can be used along with dedicated resources
+(assigning a specific cluster to an account) to effectively offer
+different levels of service to different accounts. For example, an
+account paying for a more expensive level of service could be assigned
+to a dedicated cluster with an over-provisioning ratio of 1, and a
+lower-paying account to a cluster with a ratio of 2.
+
+When a new host is added to a cluster, CloudStack will assume the host
+has the capability to perform the CPU and RAM over-provisioning which is
+configured for that cluster. It is up to the administrator to be sure
+the host is actually suitable for the level of over-provisioning which
+has been set.
+
+
+Limitations on Over-Provisioning in XenServer and KVM
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+-  In XenServer, due to a constraint of this hypervisor, you can not use
+   an over-provisioning factor greater than 4.
+
+-  The KVM hypervisor can not manage memory allocation to VMs
+   dynamically. CloudStack sets the minimum and maximum amount of memory
+   that a VM can use. The hypervisor adjusts the memory within the set
+   limits based on the memory contention.
+
+
+Requirements for Over-Provisioning
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+Several prerequisites are required in order for over-provisioning to
+function properly. The feature is dependent on the OS type, hypervisor
+capabilities, and certain scripts. It is the administrator's
+responsibility to ensure that these requirements are met.
+
+
+Balloon Driver
+^^^^^^^^^^^^^^
+
+All VMs should have a balloon driver installed in them. The hypervisor
+communicates with the balloon driver to free up and make the memory
+available to a VM.
+
+
+XenServer
+'''''''''
+
+The balloon driver can be found as a part of xen pv or PVHVM drivers.
+The xen pvhvm drivers are included in upstream linux kernels 2.6.36+.
+
+
+VMware
+''''''
+
+The balloon driver can be found as a part of the VMware tools. All the
+VMs that are deployed in a over-provisioned cluster should have the
+VMware tools installed.
+
+
+KVM
+'''
+
+All VMs are required to support the virtio drivers. These drivers are
+installed in all Linux kernel versions 2.6.25 and greater. The
+administrator must set CONFIG\_VIRTIO\_BALLOON=y in the virtio
+configuration.
+
+
+Hypervisor capabilities
+^^^^^^^^^^^^^^^^^^^^^^^
+
+The hypervisor must be capable of using the memory ballooning.
+
+
+XenServer
+'''''''''
+
+The DMC (Dynamic Memory Control) capability of the hypervisor should be
+enabled. Only XenServer Advanced and above versions have this feature.
+
+
+VMware, KVM
+'''''''''''
+
+Memory ballooning is supported by default.
+
+
+Setting Over-Provisioning Ratios
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+There are two ways the root admin can set CPU and RAM over-provisioning
+ratios. First, the global configuration settings
+cpu.overprovisioning.factor and mem.overprovisioning.factor will be
+applied when a new cluster is created. Later, the ratios can be modified
+for an existing cluster.
+
+Only VMs deployed after the change are affected by the new setting. If
+you want VMs deployed before the change to adopt the new
+over-provisioning ratio, you must stop and restart the VMs. When this is
+done, CloudStack recalculates or scales the used and reserved capacities
+based on the new over-provisioning ratios, to ensure that CloudStack is
+correctly tracking the amount of free capacity.
+
+.. note:: 
+   It is safer not to deploy additional new VMs while the capacity 
+   recalculation is underway, in case the new values for available 
+   capacity are not high enough to accommodate the new VMs. Just wait 
+   for the new used/available values to become available, to be sure 
+   there is room for all the new VMs you want.
+
+To change the over-provisioning ratios for an existing cluster:
+
+#. Log in as administrator to the CloudStack UI.
+
+#. In the left navigation bar, click Infrastructure.
+
+#. Under Clusters, click View All.
+
+#. Select the cluster you want to work with, and click the Edit button.
+
+#. Fill in your desired over-provisioning multipliers in the fields CPU
+   overcommit ratio and RAM overcommit ratio. The value which is
+   intially shown in these fields is the default value inherited from
+   the global configuration settings.
+
+   .. note:: 
+      In XenServer, due to a constraint of this hypervisor, you can not 
+      use an over-provisioning factor greater than 4.
+
+
+Service Offering Limits and Over-Provisioning
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+Service offering limits (e.g. 1 GHz, 1 core) are strictly enforced for
+core count. For example, a guest with a service offering of one core
+will have only one core available to it regardless of other activity on
+the Host.
+
+Service offering limits for gigahertz are enforced only in the presence
+of contention for CPU resources. For example, suppose that a guest was
+created with a service offering of 1 GHz on a Host that has 2 GHz cores,
+and that guest is the only guest running on the Host. The guest will
+have the full 2 GHz available to it. When multiple guests are attempting
+to use the CPU a weighting factor is used to schedule CPU resources. The
+weight is based on the clock speed in the service offering. Guests
+receive a CPU allocation that is proportionate to the GHz in the service
+offering. For example, a guest created from a 2 GHz service offering
+will receive twice the CPU allocation as a guest created from a 1 GHz
+service offering. CloudStack does not perform memory over-provisioning.
+
+
+VLAN Provisioning
+-----------------
+
+CloudStack automatically creates and destroys interfaces bridged to
+VLANs on the hosts. In general the administrator does not need to manage
+this process.
+
+CloudStack manages VLANs differently based on hypervisor type. For
+XenServer or KVM, the VLANs are created on only the hosts where they
+will be used and then they are destroyed when all guests that require
+them have been terminated or moved to another host.
+
+For vSphere the VLANs are provisioned on all hosts in the cluster even
+if there is no guest running on a particular Host that requires the
+VLAN. This allows the administrator to perform live migration and other
+functions in vCenter without having to create the VLAN on the
+destination Host. Additionally, the VLANs are not removed from the Hosts
+when they are no longer needed.
+
+You can use the same VLANs on different physical networks provided that
+each physical network has its own underlying layer-2 infrastructure,
+such as switches. For example, you can specify VLAN range 500 to 1000
+while deploying physical networks A and B in an Advanced zone setup.
+This capability allows you to set up an additional layer-2 physical
+infrastructure on a different physical NIC and use the same set of VLANs
+if you run out of VLANs. Another advantage is that you can use the same
+set of IPs for different customers, each one with their own routers and
+the guest networks on different physical NICs.
+
+
+VLAN Allocation Example
+~~~~~~~~~~~~~~~~~~~~~~~
+
+VLANs are required for public and guest traffic. The following is an
+example of a VLAN allocation scheme:
+
+.. cssclass:: table-striped table-bordered table-hover
+
+=================   =============================   ====================================================================================================
+VLAN IDs            Traffic type                    Scope
+=================   =============================   ====================================================================================================
+less than 500       Management traffic.             Reserved for administrative purposes.  CloudStack software can access this, hypervisors, system VMs.
+500-599             VLAN carrying public traffic.   CloudStack accounts.
+600-799             VLANs carrying guest traffic.   CloudStack accounts. Account-specific VLAN is chosen from this pool.
+800-899             VLANs carrying guest traffic.   CloudStack accounts. Account-specific VLAN chosen by CloudStack admin to assign to that account.
+900-999             VLAN carrying guest traffic     CloudStack accounts. Can be scoped by project, domain, or all accounts.
+greater than 1000   Reserved for future use
+=================   =============================   ====================================================================================================
+
+
+Adding Non Contiguous VLAN Ranges
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+CloudStack provides you with the flexibility to add non contiguous VLAN
+ranges to your network. The administrator can either update an existing
+VLAN range or add multiple non contiguous VLAN ranges while creating a
+zone. You can also use the UpdatephysicalNetwork API to extend the VLAN
+range.
+
+#. Log in to the CloudStack UI as an administrator or end user.
+
+#. Ensure that the VLAN range does not already exist.
+
+#. In the left navigation, choose Infrastructure.
+
+#. On Zones, click View More, then click the zone to which you want to
+   work with.
+
+#. Click Physical Network.
+
+#. In the Guest node of the diagram, click Configure.
+
+#. Click Edit |edit-icon.png|.
+
+   The VLAN Ranges field now is editable.
+
+#. Specify the start and end of the VLAN range in comma-separated list.
+
+   Specify all the VLANs you want to use, VLANs not specified will be
+   removed if you are adding new ranges to the existing list.
+
+#. Click Apply.
+
+
+Assigning VLANs to Isolated Networks
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+CloudStack provides you the ability to control VLAN assignment to
+Isolated networks. As a Root admin, you can assign a VLAN ID when a
+network is created, just the way it's done for Shared networks.
+
+The former behaviour also is supported — VLAN is randomly allocated to a
+network from the VNET range of the physical network when the network
+turns to Implemented state. The VLAN is released back to the VNET pool
+when the network shuts down as a part of the Network Garbage Collection.
+The VLAN can be re-used either by the same network when it is
+implemented again, or by any other network. On each subsequent
+implementation of a network, a new VLAN can be assigned.
+
+Only the Root admin can assign VLANs because the regular users or domain
+admin are not aware of the physical network topology. They cannot even
+view what VLAN is assigned to a network.
+
+To enable you to assign VLANs to Isolated networks,
+
+#. Create a network offering by specifying the following:
+
+   -  **Guest Type**: Select Isolated.
+
+   -  **Specify VLAN**: Select the option.
+
+   For more information, see the CloudStack Installation Guide.
+
+#. Using this network offering, create a network.
+
+   You can create a VPC tier or an Isolated network.
+
+#. Specify the VLAN when you create the network.
+
+   When VLAN is specified, a CIDR and gateway are assigned to this
+   network and the state is changed to Setup. In this state, the network
+   will not be garbage collected.
+
+.. note:: 
+   You cannot change a VLAN once it's assigned to the network. The VLAN 
+   remains with the network for its entire life cycle.
+
+
+.. |enable-disable.png| image:: /_static/images/enable-disable.png
+   :alt: button to enable or disable zone, pod, or cluster.
+.. |edit-icon.png| image:: /_static/images/edit-icon.png
+   :alt: button to edit the VLAN range.
+
+
+Out-of-band Management
+----------------------
+
+CloudStack provides Root admins the ability to configure and use supported
+out-of-band management interface (e.g. IPMI, iLO, DRAC, etc.) on a physical
+host to manage host power operations such as on, off, reset etc. By default,
+IPMI 2.0 baseboard controller are supported out of the box with ``IPMITOOL``
+out-of-band management driver in CloudStack that uses ``ipmitool`` for performing
+IPMI 2.0 management operations.
+
+Following are some global settings that control various aspects of this feature.
+
+.. cssclass:: table-striped table-bordered table-hover
+
+=======================================   =============================   ====================================================================================================
+Global setting                            Default values                  Description
+=======================================   =============================   ====================================================================================================
+outofbandmanagement.action.timeout        60                              The out of band management action timeout in seconds, configurable per cluster
+outofbandmanagement.ipmitool.interface    lanplus                         The out of band management IpmiTool driver interface to use. Valid values are: lan, lanplus etc
+outofbandmanagement.ipmitool.path         /usr/bin/ipmitool               The out of band management ipmitool path used by the IpmiTool driver
+outofbandmanagement.ipmitool.retries      1                               The out of band management IpmiTool driver retries option -R
+outofbandmanagement.sync.poolsize         50                              The out of band management background sync thread pool size 50
+=======================================   =============================   ====================================================================================================
+
+A change in ``outofbandmanagement.sync.poolsize`` settings requires restarting of
+management server(s) as the thread pool and a background (power state) sync
+thread are configured during load time when CloudStack management server starts.
+Rest of the global settings can be changed without requiring restarting of
+management server(s).
+
+The ``outofbandmanagement.sync.poolsize`` is the maximum number of ipmitool
+background power state scanners that can run at a time. Based on the maximum
+number of hosts you've, you can increase/decrease the value depending on how much
+stress your management server host can endure. It will take atmost number of
+total out-of-band-management enabled hosts in a round *
+``outofbandmanagement.action.timeout`` / ``outofbandmanagement.sync.poolsize`` seconds
+to complete a background power-state sync scan in a single round.
+
+In order to use this feature, the Root admin needs to first configure
+out-of-band management for a host using either the UI or the
+``configureOutOfBandManagement`` API. Next, the Root admin needs to enable it.
+The feature can be enabled or disabled across a zone or a cluster or a host,
+
+Once out-of-band management is configured and enabled for a host (and provided
+not disabled at zone or cluster level), Root admins would be able to issue
+power management actions such as on, off, reset, cycle, soft and status.
+
+If a host is in maintenance mode, Root admins are still allowed to perform
+power management actions but in the UI a warning is displayed.
+
+.. _host-security:
+
+Security
+--------
+
+Starting 4.11, CloudStack has an inbuilt certicate authority (CA) framework and
+a default 'root' CA provider which acts as a self-signed CA. The CA framework
+participates in certificate issuance, renewal, revocation, and propagation of
+certificates during setup of a host. This framework is primary used to
+secure communications between CloudStack management server(s), the
+KVM/LXC/SSVM/CPVM agent(s) and peer management server(s).
+
+Following are some global settings that control various aspects of this feature.
+
+.. cssclass:: table-striped table-bordered table-hover
+
+=======================================   ====================================================================
+Global setting                            Description
+=======================================   ====================================================================
+ca.framework.provider.plugin              The configured CA provider plugin
+ca.framework.cert.keysize                 The key size used for certificate generation
+ca.framework.cert.signature.algorithm     The certificate signature algorithm
+ca.framework.cert.validity.period         Certificate validity in days
+ca.framework.cert.automatic.renewal       Whether to auto-renew expiring certificate on hosts
+ca.framework.background.task.delay        The delay between each CA background task round in seconds
+ca.framework.cert.expiry.alert.period     The number of days to check and alert expiring certificates
+ca.plugin.root.private.key                (hidden/encrypted in database) Auto-generated CA private key
+ca.plugin.root.public.key                 (hidden/encrypted in database) CA public key
+ca.plugin.root.ca.certificate             (hidden/encrypted in database) CA certificate
+ca.plugin.root.issuer.dn                  The CA issue distinguished name used by the root CA provider
+ca.plugin.root.auth.strictness            Setting to enforce two-way SSL authentication and trust validation
+ca.plugin.root.allow.expired.cert         Setting to allow clients with expired certificates
+=======================================   ====================================================================
+
+A change in ``ca.framework.background.task.delay`` settings requires restarting of
+management server(s) as the thread pool and a background tasks are configured
+only when CloudStack management server(s) start.
+
+After upgrade to CloudStack 4.11+, the CA framework will by default use the
+``root`` CA provider. This CA provider will auto-generate its private/public keys
+and CA certificate on first boot post-upgrade. For freshly installed
+environments, the ``ca.plugin.root.auth.strictness`` setting will be ``true`` to
+enforce two-way SSL authentication and trust validation between client and
+server components, however, it will be ``false`` on upgraded environments to
+be backward compatible with legacy behaviour of trusting all clients and
+servers, and one-way SSL authentication. Upgraded/existing environments can
+use the ``provisionCertificate`` API to renew/setup certificates for already
+connected agents/hosts, and once all the agents/hosts are secured they may
+enforce authentication and validation strictness by setting
+``ca.plugin.root.auth.strictness`` to ``true`` and restarting the management
+server(s).
+
+Server Address Usage
+--------------------
+
+Historically, when multiple management servers are used a tcp-LB is used on
+port 8250 (default) of the management servers and the VIP/LB-IP is used as the
+``host`` setting to be used by various CloudStack agents such as the KVM, CPVM,
+SSVM agents, who connect to the ``host`` on port 8250. However, starting
+CloudStack 4.11+ the ``host`` setting can accept comma separated list of
+management server IPs to which new CloudStack hosts/agents will get a shuffled
+list of the same to which they can cycle reconnections in a round-robin way.
+
+Securing Process
+----------------
+
+Agents while making connections/reconnections to management server will only
+validate server certificate and be able to present client certificate (issued to
+them) when ``cloud.jks`` is accessible to them. On older hosts that are setup
+prior to this feature the keystore won't be available, however, they can still
+connect to management server(s) if ``ca.plugin.root.auth.strictness`` is set to
+``false``. Management server(s) will check and setup their own ``cloud.jks``
+keystore on startup, this keystore will be used for connecting to peer
+management server(s).
+
+When a new host is being setup, such as adding a KVM host or starting a systemvm
+host, the CA framework kicks in and uses ssh to execute ``keystore-setup`` to
+generate a new keystore file ``cloud.jks.new``, save a random passphrase of the
+keystore in the agent's properties file and a CSR ``cloud.csr`` file. The CSR is
+then used to issue certificate for that agent/host and ssh is used to execute
+``keystore-cert-import`` to import the issued certificate along with the CA
+certificate(s), the keystore is that renamed as ``cloud.jks`` replacing an
+previous keystore in-use. During this process, keys and certificates files are
+also stored in ``cloud.key``, ``cloud.crt``, ``cloud.ca.crt`` in the
+agent's configuration directory.
+
+When hosts are added out-of-band, for example a KVM host that is setup first
+outside of CloudStack and added to a cluster, the keystore file will not be
+available however the keystore and security could be setup by using keystore
+utility scripts manually. The ``keystore-setup`` can be ran first to generate a
+keystore and a CSR, then CloudStack CA can be used to issue certificate by
+providing the CSR to the ``issueCertificate`` API, and finally issued certificate
+and CA certificate(s) can be imported to the keystore using ``keystore-cert-import``
+script.
+
+Following lists the usage of these scripts, when using these script use full
+paths, use the final keystore filename as ``cloud.jks``, and the certificate/key
+content need to be encoded and provided such that newlines are replace with ``^``
+and space are replaced with ``~``:
+
+.. code:: bash
+
+  keystore-setup <properties file> <keystore file> <passphrase> <validity> <csr file>
+
+  keystore-cert-import <properties file> <keystore file> <mode: ssh|agent> <cert file> <cert content> <ca-cert file> <ca-cert content> <private-key file> <private key content:optional>
+
+Starting 4.11.1, a KVM host is considered secured when it has its keystore and
+certificates setup for both the agent and libvirtd process. A secured host will
+only allow and initiate TLS enabled live VM migration. This requires libvirtd
+to listen on default port 16514, and the port to be allowed in the firewall
+rules. Certificate renewal (using the ``provisionCertificate`` API) will restart
+both the libvirtd process and agent after deploying new certificates.
diff --git a/source/adminguide/index.rst b/source/adminguide/index.rst
new file mode 100644
index 0000000..15ed4d0
--- /dev/null
+++ b/source/adminguide/index.rst
@@ -0,0 +1,173 @@
+.. Licensed to the Apache Software Foundation (ASF) under one
+   or more contributor license agreements.  See the NOTICE file
+   distributed with this work for additional information#
+   regarding copyright ownership.  The ASF licenses this file
+   to you under the Apache License, Version 2.0 (the
+   "License"); you may not use this file except in compliance
+   with the License.  You may obtain a copy of the License at
+   http://www.apache.org/licenses/LICENSE-2.0
+   Unless required by applicable law or agreed to in writing,
+   software distributed under the License is distributed on an
+   "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+   KIND, either express or implied.  See the License for the
+   specific language governing permissions and limitations
+   under the License.
+
+.. CloudStack Administration Documentation master file, created by
+   sphinx-quickstart on Sat Jan 25 15:55:12 2014.
+   You can adapt this file completely to your liking, but it should at least
+   contain the root `toctree` directive.
+
+
+|menu_acs_logo|
+
+
+Usage Guide
+===========
+
+This guide is aimed at Administrators of a CloudStack based Cloud
+
+User Interface
+--------------
+
+.. toctree::
+   :maxdepth: 4
+
+   ui
+
+
+Managing Accounts, Users and Domains
+------------------------------------
+
+.. toctree::
+   :maxdepth: 4
+
+   accounts
+
+
+Using Projects to Organize User Resources
+------------------------------------------
+.. toctree::
+   :maxdepth: 4 
+
+   projects
+
+
+Service Offerings
+-----------------
+
+.. toctree::
+   :maxdepth: 4
+
+   service_offerings
+
+
+Setting up Networking for Users
+-------------------------------
+
+.. toctree::
+   :maxdepth: 4
+
+   networking
+   autoscale_without_netscaler
+
+
+Working with Virtual Machines
+-----------------------------
+
+.. toctree::
+   :maxdepth: 4
+
+   virtual_machines
+
+
+Working with Templates
+----------------------
+
+.. toctree::
+   :maxdepth: 4
+
+   templates
+
+
+Working with Hosts
+------------------
+
+.. toctree::
+   :maxdepth: 4
+
+   hosts
+
+
+Working with Storage
+--------------------
+
+.. toctree::
+   :maxdepth: 4
+
+   storage
+
+
+Working with System Virtual Machines
+------------------------------------
+
+.. toctree::
+   :maxdepth: 4
+
+   systemvm
+
+
+Working with Usage
+------------------
+
+.. toctree::
+   :maxdepth: 4
+
+   usage
+
+
+Managing Networks and Traffic
+-----------------------------
+
+.. toctree::
+   :maxdepth: 4
+
+   networking_and_traffic
+   networking/using_remote_access
+
+
+Managing the Cloud
+------------------
+
+.. toctree::
+   :maxdepth: 4
+
+   management
+
+
+System Reliability and Availability
+-----------------------------------
+
+.. toctree::
+   :maxdepth: 4
+
+   reliability
+
+
+Tuning
+------
+
+.. toctree::
+   :maxdepth: 4
+
+   tuning
+
+
+Events and Troubleshooting
+--------------------------
+
+.. toctree::
+   :maxdepth: 4
+
+   events
+   troubleshooting
diff --git a/source/adminguide/locale/pot/accounts.pot b/source/adminguide/locale/pot/accounts.pot
new file mode 100644
index 0000000..2bc6819
--- /dev/null
+++ b/source/adminguide/locale/pot/accounts.pot
@@ -0,0 +1,409 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 
+# This file is distributed under the same license as the Apache CloudStack Administration Documentation package.
+# FIRST AUTHOR <EM...@ADDRESS>, YEAR.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: Apache CloudStack Administration Documentation 4\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2014-06-30 12:52+0200\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EM...@ADDRESS>\n"
+"Language-Team: LANGUAGE <LL...@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#: ../../accounts.rst:18
+# bdc151e73be141a8ad0b4190c3102939
+msgid "Managing Accounts, Users and Domains"
+msgstr ""
+
+#: ../../accounts.rst:21
+# a49422e951994e72894009f0fc5cc963
+msgid "Accounts, Users, and Domains"
+msgstr ""
+
+#: ../../accounts.rst:24
+# 7316ca3f637249cbbf2f29bd75791600
+msgid "Accounts"
+msgstr ""
+
+#: ../../accounts.rst:26
+# 7544ce31af194b279c9dcfb7ae37d3cc
+msgid "An account typically represents a customer of the service provider or a department in a large organization. Multiple users can exist in an account."
+msgstr ""
+
+#: ../../accounts.rst:32
+# e758840629a8483ba31892ff437911e1
+msgid "Domains"
+msgstr ""
+
+#: ../../accounts.rst:34
+# 3e28d2a36b0642c08a698f6a4426e72c
+msgid "Accounts are grouped by domains. Domains usually contain multiple accounts that have some logical relationship to each other and a set of delegated administrators with some authority over the domain and its subdomains. For example, a service provider with several resellers could create a domain for each reseller."
+msgstr ""
+
+#: ../../accounts.rst:40
+# 79060520f2e046868f58925f3f2efc01
+msgid "For each account created, the Cloud installation creates three different types of user accounts: root administrator, domain administrator, and user."
+msgstr ""
+
+#: ../../accounts.rst:46
+# 341bf7792d884c2d8180600a07351f62
+msgid "Users"
+msgstr ""
+
+#: ../../accounts.rst:48
+# 8efee3ca63e44a4098ff5086e58f1249
+msgid "Users are like aliases in the account. Users in the same account are not isolated from each other, but they are isolated from users in other accounts. Most installations need not surface the notion of users; they just have one user per account. The same user cannot belong to multiple accounts."
+msgstr ""
+
+#: ../../accounts.rst:54
+# 67a573904306470f87a1f3f6ad52a15f
+msgid "Username is unique in a domain across accounts in that domain. The same username can exist in other domains, including sub-domains. Domain name can repeat only if the full pathname from root is unique. For example, you can create root/d1, as well as root/foo/d1, and root/sales/d1."
+msgstr ""
+
+#: ../../accounts.rst:59
+# af85977a7aeb4aff9010bde059e08b23
+msgid "Administrators are accounts with special privileges in the system. There may be multiple administrators in the system. Administrators can create or delete other administrators, and change the password for any user in the system."
+msgstr ""
+
+#: ../../accounts.rst:66
+# 8613eb42958647fba87ae1b922d58740
+msgid "Domain Administrators"
+msgstr ""
+
+#: ../../accounts.rst:68
+# 901efdb2c8554033b865587a48a319f9
+msgid "Domain administrators can perform administrative operations for users who belong to that domain. Domain administrators do not have visibility into physical servers or other domains."
+msgstr ""
+
+#: ../../accounts.rst:74
+# 5922a532b5814e479301a7d697eb8854
+msgid "Root Administrator"
+msgstr ""
+
+#: ../../accounts.rst:76
+# 20be104d0a134bab92309e774b538dd4
+msgid "Root administrators have complete access to the system, including managing templates, service offerings, customer care administrators, and domains"
+msgstr ""
+
+#: ../../accounts.rst:82
+# 7f9e7eaa9c5b4eaba5575b81514d4040
+msgid "Resource Ownership"
+msgstr ""
+
+#: ../../accounts.rst:84
+# 3fad6f5edfb34464b707419ce6b7b4a6
+msgid "Resources belong to the account, not individual users in that account. For example, billing, resource limits, and so on are maintained by the account, not the users. A user can operate on any resource in the account provided the user has privileges for that operation. The privileges are determined by the role. A root administrator can change the ownership of any virtual machine from one account to any other account by using the assignVirtualMachine API. A domain or sub-domain admi [...]
+msgstr ""
+
+#: ../../accounts.rst:96
+# f25ec45041cd435d83eaf32720407dd4
+msgid "Dedicating Resources to Accounts and Domains"
+msgstr ""
+
+#: ../../accounts.rst:98
+# 8a6427fc034647e681a14ca03224406c
+msgid "The root administrator can dedicate resources to a specific domain or account that needs private infrastructure for additional security or performance guarantees. A zone, pod, cluster, or host can be reserved by the root administrator for a specific domain or account. Only users in that domain or its subdomain may use the infrastructure. For example, only users in a given domain can create guests in a zone dedicated to that domain."
+msgstr ""
+
+#: ../../accounts.rst:106
+# 13b20e92d1144d5da1089384a9ce4e59
+msgid "There are several types of dedication available:"
+msgstr ""
+
+#: ../../accounts.rst:108
+# a62e7433baeb444386932b41fe5601fa
+msgid "Explicit dedication. A zone, pod, cluster, or host is dedicated to an account or domain by the root administrator during initial deployment and configuration."
+msgstr ""
+
+#: ../../accounts.rst:112
+# 29fbffa86cfd49b4aa29ea7d373eaa03
+msgid "Strict implicit dedication. A host will not be shared across multiple accounts. For example, strict implicit dedication is useful for deployment of certain types of applications, such as desktops, where no host can be shared between different accounts without violating the desktop software's terms of license."
+msgstr ""
+
+#: ../../accounts.rst:118
+# a821acd0f71541708e12788d2fbc5d75
+msgid "Preferred implicit dedication. The VM will be deployed in dedicated infrastructure if possible. Otherwise, the VM can be deployed in shared infrastructure."
+msgstr ""
+
+#: ../../accounts.rst:124
+# b498c9fe36a94f2588d7a9e4494a761d
+msgid "How to Dedicate a Zone, Cluster, Pod, or Host to an Account or Domain"
+msgstr ""
+
+#: ../../accounts.rst:126
+# 62ce22c4d6f346b79218ff7a937ee3e2
+msgid "For explicit dedication: When deploying a new zone, pod, cluster, or host, the root administrator can click the Dedicated checkbox, then choose a domain or account to own the resource."
+msgstr ""
+
+#: ../../accounts.rst:130
+# 9dfe3b7a9e87411d9694c32c5e4f891e
+msgid "To explicitly dedicate an existing zone, pod, cluster, or host: log in as the root admin, find the resource in the UI, and click the Dedicate button. |button to dedicate a zone, pod,cluster, or host|"
+msgstr ""
+
+#: ../../accounts.rst:134
+# 90707af3ed2b4e6fa7875e9bdd890252
+msgid "For implicit dedication: The administrator creates a compute service offering and in the Deployment Planner field, chooses ImplicitDedicationPlanner. Then in Planner Mode, the administrator specifies either Strict or Preferred, depending on whether it is permissible to allow some use of shared resources when dedicated resources are not available. Whenever a user creates a VM based on this service offering, it is allocated on one of the dedicated hosts."
+msgstr ""
+
+#: ../../accounts.rst:144
+# fda3697ce3a4454da72edbe9f02b3564
+msgid "How to Use Dedicated Hosts"
+msgstr ""
+
+#: ../../accounts.rst:146
+# cfd0e245a5a2498b9fa7c89160957ffe
+msgid "To use an explicitly dedicated host, use the explicit-dedicated type of affinity group (see `“Affinity Groups” <virtual_machines.html#affinity-groups>`_). For example, when creating a new VM, an end user can choose to place it on dedicated infrastructure. This operation will succeed only if some infrastructure has already been assigned as dedicated to the user's account or domain."
+msgstr ""
+
+#: ../../accounts.rst:155
+# 86abbd3940f34e96a1ad71a01dc6339d
+msgid "Behavior of Dedicated Hosts, Clusters, Pods, and Zones"
+msgstr ""
+
+#: ../../accounts.rst:157
+# a9963e63da4e48f2a2b7b7fdad96ba29
+msgid "The administrator can live migrate VMs away from dedicated hosts if desired, whether the destination is a host reserved for a different account/domain or a host that is shared (not dedicated to any particular account or domain). CloudStack will generate an alert, but the operation is allowed."
+msgstr ""
+
+#: ../../accounts.rst:163
+# a9a8992734b0490aac5bd5e5efa45483
+msgid "Dedicated hosts can be used in conjunction with host tags. If both a host tag and dedication are requested, the VM will be placed only on a host that meets both requirements. If there is no dedicated resource available to that user that also has the host tag requested by the user, then the VM will not deploy."
+msgstr ""
+
+#: ../../accounts.rst:169
+# 694b1842b07049c094a79e240c2db934
+msgid "If you delete an account or domain, any hosts, clusters, pods, and zones that were dedicated to it are freed up. They will now be available to be shared by any account or domain, or the administrator may choose to re-dedicate them to a different account or domain."
+msgstr ""
+
+#: ../../accounts.rst:174
+# 9676e7d49a4247c0bd41a3d53e7482a1
+msgid "System VMs and virtual routers affect the behavior of host dedication. System VMs and virtual routers are owned by the CloudStack system account, and they can be deployed on any host. They do not adhere to explicit dedication. The presence of system vms and virtual routers on a host makes it unsuitable for strict implicit dedication. The host can not be used for strict implicit dedication, because the host already has VMs of a specific account (the default system account). However [...]
+msgstr ""
+
+#: ../../accounts.rst:186
+# c3ac9b9cb46f4fa7b6ea8d96adc7111e
+msgid "Using an LDAP Server for User Authentication"
+msgstr ""
+
+#: ../../accounts.rst:188
+# 4c358cdbd0ef4ea8bae9aa240f1b4e4a
+msgid "You can use an external LDAP server such as Microsoft Active Directory or ApacheDS to authenticate CloudStack end-users. Just map CloudStack accounts to the corresponding LDAP accounts using a query filter. The query filter is written using the query syntax of the particular LDAP server, and can include special wildcard characters provided by CloudStack for matching common values such as the user’s email address and name. CloudStack will search the external LDAP directory tree sta [...]
+msgstr ""
+
+#: ../../accounts.rst:199
+# 14c749c7da61408588c8e8cdaa11796c
+msgid "To set up LDAP authentication in CloudStack, call the CloudStack API command ldapConfig and provide the following:"
+msgstr ""
+
+#: ../../accounts.rst:202
+# c4708aa56b75423080f17f84ec2a37a4
+msgid "Hostname or IP address and listening port of the LDAP server"
+msgstr ""
+
+#: ../../accounts.rst:204
+# ff4d11fcc40f4d5c86ce032c3d6e6a76
+msgid "Base directory and query filter"
+msgstr ""
+
+#: ../../accounts.rst:206
+# 0b5fce75930e49b19cf1d00062c78539
+msgid "Search user DN credentials, which give CloudStack permission to search on the LDAP server"
+msgstr ""
+
+#: ../../accounts.rst:209
+# c3d66516470141c3af861a4b24f45150
+msgid "SSL keystore and password, if SSL is used"
+msgstr ""
+
+#: ../../accounts.rst:213
+# 6e565fd7b02d4a97b86b380e839f129f
+msgid "Example LDAP Configuration Commands"
+msgstr ""
+
+#: ../../accounts.rst:215
+# ee72e29a6b33456684ebcbfd012c075a
+msgid "To understand the examples in this section, you need to know the basic concepts behind calling the CloudStack API, which are explained in the Developer’s Guide."
+msgstr ""
+
+#: ../../accounts.rst:219
+# 065e58a0d0f74c8d84670251cf00c487
+msgid "The following shows an example invocation of ldapConfig with an ApacheDS LDAP server"
+msgstr ""
+
+#: ../../accounts.rst:226
+# 31d88144f8004adf8efd11cf7f9db7bd
+msgid "The command must be URL-encoded. Here is the same example without the URL encoding:"
+msgstr ""
+
+#: ../../accounts.rst:244
+# 884cde7f5dbd499ba1c28ff09380c692
+msgid "The following shows a similar command for Active Directory. Here, the search base is the testing group within a company, and the users are matched up based on email address."
+msgstr ""
+
+#: ../../accounts.rst:252
+# d2675a267aa34f4ea3fe2bba2300b61c
+msgid "The next few sections explain some of the concepts you will need to know when filling out the ldapConfig parameters."
+msgstr ""
+
+#: ../../accounts.rst:257
+# befdce0cfd624549844139c917a82bb4
+msgid "Search Base"
+msgstr ""
+
+#: ../../accounts.rst:259
+# 1522f19d5a2a4e35a8bedc5d147a1af1
+msgid "An LDAP query is relative to a given node of the LDAP directory tree, called the search base. The search base is the distinguished name (DN) of a level of the directory tree below which all users can be found. The users can be in the immediate base directory or in some subdirectory. The search base may be equivalent to the organization, group, or domain name. The syntax for writing a DN varies depending on which LDAP server you are using. A full discussion of distinguished names i [...]
+msgstr ""
+
+#: ../../accounts.rst:270
+#: ../../accounts.rst:328
+# 3649e87915d24059beec30463e0abd10
+# eb0f32160dd24b21991c2f454df60742
+msgid "LDAP Server"
+msgstr ""
+
+#: ../../accounts.rst:270
+# d8fb5f498afb4ee1aa6669b39f1e34be
+msgid "Example Search Base DN"
+msgstr ""
+
+#: ../../accounts.rst:272
+#: ../../accounts.rst:330
+# 2e421fc0d49d4a819b31999dc3cae2e0
+# a0327a00878d45dab6dc0bc777814674
+msgid "ApacheDS"
+msgstr ""
+
+#: ../../accounts.rst:272
+# 6c854d5e6cdd4e3aadda7dd9be769a53
+msgid "OU=testing, O=project"
+msgstr ""
+
+#: ../../accounts.rst:273
+#: ../../accounts.rst:331
+# a1fbaf989c584a248386911c51fd2fba
+# c776e850eb3e4d64b262a32a9d302bfb
+msgid "Active Directory"
+msgstr ""
+
+#: ../../accounts.rst:273
+# 5d0095ff2d7044e7b60bc1754210dd3c
+msgid "OU=testing, DC=company"
+msgstr ""
+
+#: ../../accounts.rst:278
+# 8309dae488944f0aae3e84a8e1a97ac3
+msgid "Query Filter"
+msgstr ""
+
+#: ../../accounts.rst:280
+# c523dbbf5dd94c62a2e3927a8f3123dc
+msgid "The query filter is used to find a mapped user in the external LDAP server. The query filter should uniquely map the CloudStack user to LDAP user for a meaningful authentication. For more information about query filter syntax, consult the documentation for your LDAP server."
+msgstr ""
+
+#: ../../accounts.rst:285
+# f4f9c13ceefa4163962bd3cfab257852
+msgid "The CloudStack query filter wildcards are:"
+msgstr ""
+
+#: ../../accounts.rst:288
+# bab683973b9045339c8df3488bc5dd1c
+msgid "Query Filter Wildcard"
+msgstr ""
+
+#: ../../accounts.rst:288
+# a94af335cc864d9a962f1fb9b7b5f72c
+msgid "Description"
+msgstr ""
+
+#: ../../accounts.rst:290
+# 334393ba6786415e91a2ed1a22d26adb
+msgid "%u"
+msgstr ""
+
+#: ../../accounts.rst:290
+# 151cd28e952d4ff98ff9d1544698ccb8
+msgid "User name"
+msgstr ""
+
+#: ../../accounts.rst:291
+# f1f86cbcf39e412fb298da7653a123d3
+msgid "%e"
+msgstr ""
+
+#: ../../accounts.rst:291
+# fdf52531788c41fabb814f45f07b178a
+msgid "Email address"
+msgstr ""
+
+#: ../../accounts.rst:292
+# 6e5b529e3da248ee85f1e20f81bd8e1c
+msgid "%n"
+msgstr ""
+
+#: ../../accounts.rst:292
+# 4704eb3b3e494ad3bc2105d98a3c84a9
+msgid "First and last name"
+msgstr ""
+
+#: ../../accounts.rst:295
+# 51612c6475e246f7b7d8a156605a2323
+msgid "The following examples assume you are using Active Directory, and refer to user attributes from the Active Directory schema."
+msgstr ""
+
+#: ../../accounts.rst:298
+# d853815e3f894dcdbb92be883305dc5b
+msgid "If the CloudStack user name is the same as the LDAP user ID:"
+msgstr ""
+
+#: ../../accounts.rst:304
+# d0bb623240d0410eb8d70ed22ba5a2f8
+msgid "If the CloudStack user name is the LDAP display name:"
+msgstr ""
+
+#: ../../accounts.rst:310
+# 0a96c3c2516946c1b4260fd4d4d6ffb7
+msgid "To find a user by email address:"
+msgstr ""
+
+#: ../../accounts.rst:318
+# 5b63c901fb5a4d208df8e362234d1cba
+msgid "Search User Bind DN"
+msgstr ""
+
+#: ../../accounts.rst:320
+# 92769f4cb5be444cab0bcb685ebe1cc4
+msgid "The bind DN is the user on the external LDAP server permitted to search the LDAP directory within the defined search base. When the DN is returned, the DN and passed password are used to authenticate the CloudStack user with an LDAP bind. A full discussion of bind DNs is outside the scope of our documentation. The following table shows some examples of bind DNs."
+msgstr ""
+
+#: ../../accounts.rst:328
+# 7fcc45a0be9241b09a01d2287541d652
+msgid "Example Bind DN"
+msgstr ""
+
+#: ../../accounts.rst:330
+# b4c0b2f84be54e32820cac392b6c9c75
+msgid "CN=Administrator,DC=testing,OU=project,OU=org"
+msgstr ""
+
+#: ../../accounts.rst:331
+# 46e145ddbc9f47e08b21fa2631ed9fa7
+msgid "CN=Administrator, OU=testing, DC=company, DC=com"
+msgstr ""
+
+#: ../../accounts.rst:336
+# cbaaf7054abf480eb88b336ba62a097b
+msgid "SSL Keystore Path and Password"
+msgstr ""
+
+#: ../../accounts.rst:338
+# 8a6a84c57cc144edb9a20e63c71ddedc
+msgid "If the LDAP server requires SSL, you need to enable it in the ldapConfig command by setting the parameters ssl, truststore, and truststorepass. Before enabling SSL for ldapConfig, you need to get the certificate which the LDAP server is using and add it to a trusted keystore. You will need to know the path to the keystore and the password."
+msgstr ""
+
diff --git a/source/adminguide/locale/pot/administration.pot b/source/adminguide/locale/pot/administration.pot
new file mode 100644
index 0000000..4c7627a
--- /dev/null
+++ b/source/adminguide/locale/pot/administration.pot
@@ -0,0 +1,63 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 
+# This file is distributed under the same license as the Apache CloudStack Administration Documentation package.
+# FIRST AUTHOR <EM...@ADDRESS>, YEAR.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: Apache CloudStack Administration Documentation 4\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2014-06-30 12:52+0200\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EM...@ADDRESS>\n"
+"Language-Team: LANGUAGE <LL...@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#: ../../administration.rst:18
+# 29cfff43a2514946ad4c3499ebefbed6
+msgid "User Services"
+msgstr ""
+
+#: ../../administration.rst:20
+# d7001feee3bd4b298a4c17869c0c45dc
+msgid "In addition to the physical and logical infrastructure of your cloud and the CloudStack software and servers, you also need a layer of user services so that people can actually make use of the cloud. This means not just a user UI, but a set of options and resources that users can choose from, such as templates for creating virtual machines, disk storage, and more. If you are running a commercial service, you will be keeping track of what services and resources users are consuming  [...]
+msgstr ""
+
+#: ../../administration.rst:34
+# 8691c3078d2741dabb85f469a7b58373
+msgid "Service Offerings, Disk Offerings, Network Offerings, and Templates"
+msgstr ""
+
+#: ../../administration.rst:36
+# 82a1a03c5a234653b024700134d18169
+msgid "A user creating a new instance can make a variety of choices about its characteristics and capabilities. CloudStack provides several ways to present users with choices when creating a new instance:"
+msgstr ""
+
+#: ../../administration.rst:40
+# 5b79acf1c4034cf09e56634938cbfd33
+msgid "Service Offerings, defined by the CloudStack administrator, provide a choice of CPU speed, number of CPUs, RAM size, tags on the root disk, and other choices. See Creating a New Compute Offering."
+msgstr ""
+
+#: ../../administration.rst:44
+# d71f7d3d0dda4061838347d6fc7e35fc
+msgid "Disk Offerings, defined by the CloudStack administrator, provide a choice of disk size and IOPS (Quality of Service) for primary data storage. See Creating a New Disk Offering."
+msgstr ""
+
+#: ../../administration.rst:48
+# c00720676a8a4c4a9d423dd5f5743f4c
+msgid "Network Offerings, defined by the CloudStack administrator, describe the feature set that is available to end users from the virtual router or external networking devices on a given guest network. See Network Offerings."
+msgstr ""
+
+#: ../../administration.rst:53
+# 169ad751a60e44929103a91c102ac2a2
+msgid "Templates, defined by the CloudStack administrator or by any CloudStack user, are the base OS images that the user can choose from when creating a new instance. For example, CloudStack includes CentOS as a template. See Working with Templates."
+msgstr ""
+
+#: ../../administration.rst:58
+# 81b027ebc2094409b6f28288660792c7
+msgid "In addition to these choices that are provided for users, there is another type of service offering which is available only to the CloudStack root administrator, and is used for configuring virtual infrastructure resources. For more information, see Upgrading a Virtual Router with System Service Offerings."
+msgstr ""
+
diff --git a/source/adminguide/locale/pot/api.pot b/source/adminguide/locale/pot/api.pot
new file mode 100644
index 0000000..70a1475
--- /dev/null
+++ b/source/adminguide/locale/pot/api.pot
@@ -0,0 +1,123 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 
+# This file is distributed under the same license as the Apache CloudStack Administration Documentation package.
+# FIRST AUTHOR <EM...@ADDRESS>, YEAR.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: Apache CloudStack Administration Documentation 4\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2014-06-30 12:52+0200\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EM...@ADDRESS>\n"
+"Language-Team: LANGUAGE <LL...@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#: ../../api.rst:18
+# 7499b008b97e41b59d4cdc3835758f36
+msgid "CloudStack API"
+msgstr ""
+
+#: ../../api.rst:20
+# 7a40beffc6484f108ad5202cb2a4e7c3
+msgid "The CloudStack API is a low level API that has been used to implement the CloudStack web UIs. It is also a good basis for implementing other popular APIs such as EC2/S3 and emerging DMTF standards."
+msgstr ""
+
+#: ../../api.rst:24
+# 0e4247f81b8a4a83afa84f323d2697b9
+msgid "Many CloudStack API calls are asynchronous. These will return a Job ID immediately when called. This Job ID can be used to query the status of the job later. Also, status calls on impacted resources will provide some indication of their state."
+msgstr ""
+
+#: ../../api.rst:29
+# dc0b3fef72b74085a24d7e0c15cb227d
+msgid "The API has a REST-like query basis and returns results in XML or JSON."
+msgstr ""
+
+#: ../../api.rst:31
+# 1f57015e966c480795b141ba3f87b86a
+msgid "See `the Developer’s Guide <https://cwiki.apache.org/confluence/display/CLOUDSTACK/Development+101>`_ and `the API Reference <http://cloudstack.apache.org/docs/api/>`_."
+msgstr ""
+
+#: ../../api.rst:36
+# de3d35bb699f45f495251ceb69a2c238
+msgid "Provisioning and Authentication API"
+msgstr ""
+
+#: ../../api.rst:38
+# c8eb593d2c654d8db8d5ce7791bedd07
+msgid "CloudStack expects that a customer will have their own user provisioning infrastructure. It provides APIs to integrate with these existing systems where the systems call out to CloudStack to add/remove users.."
+msgstr ""
+
+#: ../../api.rst:42
+# f37cbbabb4af4c76977b51277f5cefa3
+msgid "CloudStack supports pluggable authenticators. By default, CloudStack assumes it is provisioned with the user’s password, and as a result authentication is done locally. However, external authentication is possible as well. For example, see Using an LDAP Server for User Authentication."
+msgstr ""
+
+#: ../../api.rst:50
+# a1cd31f63e9a4fe6869e80cdd8f2274f
+msgid "User Data and Meta Data"
+msgstr ""
+
+#: ../../api.rst:52
+# 8adea5c3508040cfb6f8475bc1f2f96c
+msgid "CloudStack provides API access to attach up to 32KB of user data to a deployed VM. Deployed VMs also have access to instance metadata via the virtual router."
+msgstr ""
+
+#: ../../api.rst:56
+# 11a9a59d3f23401d8c639b7767af0a94
+msgid "User data can be accessed once the IP address of the virtual router is known. Once the IP address is known, use the following steps to access the user data:"
+msgstr ""
+
+#: ../../api.rst:60
+# 0b14bfd2cf6c41a98f39a406fdb83868
+msgid "Run the following command to find the virtual router."
+msgstr ""
+
+#: ../../api.rst:66
+# e0144a29051543d1aba1d5b18d18e033
+msgid "Access user data by running the following command using the result of the above command"
+msgstr ""
+
+#: ../../api.rst:73
+# 8ebc1946ef8840c4b4c99d6194576997
+msgid "Meta Data can be accessed similarly, using a URL of the form http://10.1.1.1/latest/meta-data/{metadata type}. (For backwards compatibility, the previous URL http://10.1.1.1/latest/{metadata type} is also supported.) For metadata type, use one of the following:"
+msgstr ""
+
+#: ../../api.rst:78
+# bed0120874a643b1b9d59bd6a4e9e404
+msgid "service-offering. A description of the VMs service offering"
+msgstr ""
+
+#: ../../api.rst:80
+# 71b8d766955140c3b512c2a9318fa115
+msgid "availability-zone. The Zone name"
+msgstr ""
+
+#: ../../api.rst:82
+# 2a80730691bb49e0b69de28d14feea03
+msgid "local-ipv4. The guest IP of the VM"
+msgstr ""
+
+#: ../../api.rst:84
+# 6f5c73e35f714f0f83b7c799a46c499f
+msgid "local-hostname. The hostname of the VM"
+msgstr ""
+
+#: ../../api.rst:86
+# ad4c5b53b2844aa9b7518ea0165e3c5a
+msgid "public-ipv4. The first public IP for the router. (E.g. the first IP of eth2)"
+msgstr ""
+
+#: ../../api.rst:89
+# 53db659838e1499c86e3674db658bbdb
+msgid "public-hostname. This is the same as public-ipv4"
+msgstr ""
+
+#: ../../api.rst:91
+# 760946f739514ea5be9f4c114716b1ba
+msgid "instance-id. The instance name of the VM"
+msgstr ""
+
diff --git a/source/adminguide/locale/pot/events.pot b/source/adminguide/locale/pot/events.pot
new file mode 100644
index 0000000..0fe5136
--- /dev/null
+++ b/source/adminguide/locale/pot/events.pot
@@ -0,0 +1,332 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 
+# This file is distributed under the same license as the Apache CloudStack Administration Documentation package.
+# FIRST AUTHOR <EM...@ADDRESS>, YEAR.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: Apache CloudStack Administration Documentation 4\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2014-06-30 12:52+0200\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EM...@ADDRESS>\n"
+"Language-Team: LANGUAGE <LL...@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#: ../../events.rst:18
+# 0defb3a9608c4824b34ed35d916fd0c4
+msgid "Event Notification"
+msgstr ""
+
+#: ../../events.rst:20
+# 37ebc4e9b0b148daaab42c65d71cc834
+msgid "An event is essentially a significant or meaningful change in the state of both virtual and physical resources associated with a cloud environment. Events are used by monitoring systems, usage and billing systems, or any other event-driven workflow systems to discern a pattern and make the right business decision. In CloudStack an event could be a state change of virtual or physical resources, an action performed by an user (action events), or policy based events (alerts)."
+msgstr ""
+
+#: ../../events.rst:30
+# 82bc7c30085140f89344da554ad386a3
+msgid "Event Logs"
+msgstr ""
+
+#: ../../events.rst:32
+# c1d54e6d1a2d4cd6888ad99bf943ed83
+msgid "There are two types of events logged in the CloudStack Event Log. Standard events log the success or failure of an event and can be used to identify jobs or processes that have failed. There are also long running job events. Events for asynchronous jobs log when a job is scheduled, when it starts, and when it completes. Other long running synchronous jobs log when a job starts, and when it completes. Long running synchronous and asynchronous event logs can be used to gain more inf [...]
+msgstr ""
+
+#: ../../events.rst:45
+# 127295678f0c4cf084cf737444f11087
+msgid "Notification"
+msgstr ""
+
+#: ../../events.rst:47
+# a669e3079b7e41d1a82dd149bf00b011
+msgid "Event notification framework provides a means for the Management Server components to publish and subscribe to CloudStack events. Event notification is achieved by implementing the concept of event bus abstraction in the Management Server. An event bus is introduced in the Management Server that allows the CloudStack components and extension plug-ins to subscribe to the events by using the Advanced Message Queuing Protocol (AMQP) client. In CloudStack, a default implementation of  [...]
+msgstr ""
+
+#: ../../events.rst:59
+# e41f3e4f6450467da27fc6dc4ebb2788
+msgid "A new event for state change, resource state change, is introduced as part of Event notification framework. Every resource, such as user VM, volume, NIC, network, public IP, snapshot, and template, is associated with a state machine and generates events as part of the state change. That implies that a change in the state of a resource results in a state change event, and the event is published in the corresponding state machine on the event bus. All the CloudStack events (alerts,  [...]
+msgstr ""
+
+#: ../../events.rst:71
+# 4aaf02080d184ab387923b45f39d5762
+msgid "Use Cases"
+msgstr ""
+
+#: ../../events.rst:73
+# f7b5a1de0f014d2eabfe925d0c5c4e95
+msgid "The following are some of the use cases:"
+msgstr ""
+
+#: ../../events.rst:75
+# 9be82bc2fe244fef9851d9adb481fdaf
+msgid "Usage or Billing Engines: A third-party cloud usage solution can implement a plug-in that can connects to CloudStack to subscribe to CloudStack events and generate usage data. The usage data is consumed by their usage software."
+msgstr ""
+
+#: ../../events.rst:80
+# 2585685666874f3f8795c70fe2671356
+msgid "AMQP plug-in can place all the events on the a message queue, then a AMQP message broker can provide topic-based notification to the subscribers."
+msgstr ""
+
+#: ../../events.rst:84
+# ff10e0227bc04e2f86f15c3c534b7c47
+msgid "Publish and Subscribe notification service can be implemented as a pluggable service in CloudStack that can provide rich set of APIs for event notification, such as topics-based subscription and notification. Additionally, the pluggable service can deal with multi-tenancy, authentication, and authorization issues."
+msgstr ""
+
+#: ../../events.rst:92
+# bdc9ac2f935c456fbd3778ddef6c91cf
+msgid "Configuration"
+msgstr ""
+
+#: ../../events.rst:94
+# c2514aa04f964044bd2bd630f31b4d3f
+msgid "As a CloudStack administrator, perform the following one-time configuration to enable event notification framework. At run time no changes can control the behaviour."
+msgstr ""
+
+#: ../../events.rst:98
+# e94d4200515d4f15adbc52ca3bbf8c54
+msgid "Open ``'componentContext.xml``."
+msgstr ""
+
+#: ../../events.rst:100
+# e2bbf37abe854d6cb8384bdd3c9d72b9
+msgid "Define a bean named ``eventNotificationBus`` as follows:"
+msgstr ""
+
+#: ../../events.rst:102
+# 47bce54d52714df7bafac2b6d04dd816
+msgid "name : Specify a name for the bean."
+msgstr ""
+
+#: ../../events.rst:104
+# 4317cb3aa0fd4c7fa3f0e637f6cfea48
+msgid "server : The name or the IP address of the RabbitMQ AMQP server."
+msgstr ""
+
+#: ../../events.rst:106
+# 0f6561172d38446db99181316f50e667
+msgid "port : The port on which RabbitMQ server is running."
+msgstr ""
+
+#: ../../events.rst:108
+# 7ff0aa3ff7af48fbbf4651a2d8e5f34d
+msgid "username : The username associated with the account to access the RabbitMQ server."
+msgstr ""
+
+#: ../../events.rst:111
+# 7193c434eaab44eda2d7d9b2b86c675d
+msgid "password : The password associated with the username of the account to access the RabbitMQ server."
+msgstr ""
+
+#: ../../events.rst:114
+# f765ea7d69504610a98a95fdb802fe32
+msgid "exchange : The exchange name on the RabbitMQ server where CloudStack events are published."
+msgstr ""
+
+#: ../../events.rst:117
+# 7ba933b1d4ec41c1a20f2cdca4275405
+msgid "A sample bean is given below:"
+msgstr ""
+
+#: ../../events.rst:130
+# 07a04a0f79804e938092a93f3180770a
+msgid "The ``eventNotificationBus`` bean represents the ``org.apache.cloudstack.mom.rabbitmq.RabbitMQEventBus`` class."
+msgstr ""
+
+#: ../../events.rst:133
+# 83cdf82ae8c34a238d181c5bbaef30dd
+msgid "Restart the Management Server."
+msgstr ""
+
+#: ../../events.rst:137
+# 573b41c4def247f6981e828da7f54f82
+msgid "Standard Events"
+msgstr ""
+
+#: ../../events.rst:139
+#: ../../events.rst:161
+# f503981d0a764de49d4acc01c70d6126
+# 9212f9cd71b542899ac8256d4a51026d
+msgid "The events log records three types of standard events."
+msgstr ""
+
+#: ../../events.rst:141
+#: ../../events.rst:163
+# fab87560ba674752808dacaf3abfc44a
+# 94b40a1c0c98456399293f6a38102385
+msgid "INFO. This event is generated when an operation has been successfully performed."
+msgstr ""
+
+#: ../../events.rst:144
+#: ../../events.rst:166
+# 49450fc963104f569e80611ac7179829
+# 13438410decf4526b0381dc44062ba76
+msgid "WARN. This event is generated in the following circumstances."
+msgstr ""
+
+#: ../../events.rst:146
+#: ../../events.rst:168
+# c6197efc809f4a67baf05aa139cb10f5
+# a16599807269441f8f1799ae29968e11
+msgid "When a network is disconnected while monitoring a template download."
+msgstr ""
+
+#: ../../events.rst:149
+#: ../../events.rst:171
+# 0e060afef9e84640b3c2da38436691e2
+# 019e604962174d4492cca7be02ad2647
+msgid "When a template download is abandoned."
+msgstr ""
+
+#: ../../events.rst:151
+#: ../../events.rst:173
+# 8b3eabd5fcc0406bb83abe3863261df9
+# 19ccb6eebbc1446a8cb47056d2ad0274
+msgid "When an issue on the storage server causes the volumes to fail over to the mirror storage server."
+msgstr ""
+
+#: ../../events.rst:154
+#: ../../events.rst:176
+# 96793fba6d294c98bd8dcde72d0d9f49
+# 0b487b0c814145438366a847c93c52d8
+msgid "ERROR. This event is generated when an operation has not been successfully performed"
+msgstr ""
+
+#: ../../events.rst:159
+# b1c1824ddd304288bd0803e80d482bb9
+msgid "Long Running Job Events"
+msgstr ""
+
+#: ../../events.rst:181
+# ffb5ee0896674a62a567e634fc725510
+msgid "Event Log Queries"
+msgstr ""
+
+#: ../../events.rst:183
+# 0c75a642e72943e0bb28642902590c9b
+msgid "Database logs can be queried from the user interface. The list of events captured by the system includes:"
+msgstr ""
+
+#: ../../events.rst:186
+# fe735d1b0444472aa47e381cd00eec61
+msgid "Virtual machine creation, deletion, and on-going management operations"
+msgstr ""
+
+#: ../../events.rst:189
+# e331126149b64023bf0e7655bbcb2991
+msgid "Virtual router creation, deletion, and on-going management operations"
+msgstr ""
+
+#: ../../events.rst:191
+# 33b99484fca246c48ceff95aac8b52d2
+msgid "Template creation and deletion"
+msgstr ""
+
+#: ../../events.rst:193
+# 7969071933104816945f05e9f3a597e3
+msgid "Network/load balancer rules creation and deletion"
+msgstr ""
+
+#: ../../events.rst:195
+# 91ecfa5192134ffeafe5043cff29432a
+msgid "Storage volume creation and deletion"
+msgstr ""
+
+#: ../../events.rst:197
+# b0c0672f35af4003870943a16b461337
+msgid "User login and logout"
+msgstr ""
+
+#: ../../events.rst:201
+# 57cfb09e85c842b581f3a0f38609a9c4
+msgid "Deleting and Archiving Events and Alerts"
+msgstr ""
+
+#: ../../events.rst:203
+# b4160055fbd946979df299cf40a75777
+msgid "CloudStack provides you the ability to delete or archive the existing alerts and events that you no longer want to implement. You can regularly delete or archive any alerts or events that you cannot, or do not want to resolve from the database."
+msgstr ""
+
+#: ../../events.rst:208
+# 7bdab572982c4739808182e94b589c7e
+msgid "You can delete or archive individual alerts or events either directly by using the Quickview or by using the Details page. If you want to delete multiple alerts or events at the same time, you can use the respective context menu. You can delete alerts or events by category for a time period. For example, you can select categories such as **USER.LOGOUT**, **VM.DESTROY**, **VM.AG.UPDATE**, **CONFIGURATION.VALUE.EDI**, and so on. You can also view the number of events or alerts archi [...]
+msgstr ""
+
+#: ../../events.rst:217
+# cf46cdd4536a4a93912df2f4e88af8a1
+msgid "In order to support the delete or archive alerts, the following global parameters have been added:"
+msgstr ""
+
+#: ../../events.rst:220
+# 19ff2e090cf24d30aeacde33ec972af1
+msgid "**alert.purge.delay**: The alerts older than specified number of days are purged. Set the value to 0 to never purge alerts automatically."
+msgstr ""
+
+#: ../../events.rst:223
+# e3ccfdc51da14488bc9e44623c64d707
+msgid "**alert.purge.interval**: The interval in seconds to wait before running the alert purge thread. The default is 86400 seconds (one day)."
+msgstr ""
+
+#: ../../events.rst:228
+# a6eda71ad15940c2b58724ff74f97e26
+msgid "Archived alerts or events cannot be viewed in the UI or by using the API. They are maintained in the database for auditing or compliance purposes."
+msgstr ""
+
+#: ../../events.rst:234
+# 7c40293965f24130896768ea8223a152
+msgid "Permissions"
+msgstr ""
+
+#: ../../events.rst:236
+# e43e679e6a304ae1b78e11f56bed12b2
+msgid "Consider the following:"
+msgstr ""
+
+#: ../../events.rst:238
+# c5bd820d9a5e487b9440609da1e22551
+msgid "The root admin can delete or archive one or multiple alerts or events."
+msgstr ""
+
+#: ../../events.rst:241
+# 51b4fa6e53064c7088052c69d7a1b4fe
+msgid "The domain admin or end user can delete or archive one or multiple events."
+msgstr ""
+
+#: ../../events.rst:246
+# bea2b3dcb4bb41468a31793133ffeb06
+msgid "Procedure"
+msgstr ""
+
+#: ../../events.rst:248
+# aa16543921984837a7f59142ad2df67d
+msgid "Log in as administrator to the CloudStack UI."
+msgstr ""
+
+#: ../../events.rst:250
+# f8b2ec5bdbf749d2bf704ff20c063c89
+msgid "In the left navigation, click Events."
+msgstr ""
+
+#: ../../events.rst:252
+# 5519a86ae5b04a68b972ee88e37deffe
+msgid "Perform either of the following:"
+msgstr ""
+
+#: ../../events.rst:254
+# fd1193e3ff83466aa226d4834dea269d
+msgid "To archive events, click Archive Events, and specify event type and date."
+msgstr ""
+
+#: ../../events.rst:257
+# abfda9e22c7f42f3a4ff488ff755e59e
+msgid "To archive events, click Delete Events, and specify event type and date."
+msgstr ""
+
+#: ../../events.rst:260
+# 58b630d17160410ab6757d134aa17a62
+msgid "Click OK."
+msgstr ""
+
diff --git a/source/adminguide/locale/pot/hosts.pot b/source/adminguide/locale/pot/hosts.pot
new file mode 100644
index 0000000..6314be5
--- /dev/null
+++ b/source/adminguide/locale/pot/hosts.pot
@@ -0,0 +1,828 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 
+# This file is distributed under the same license as the Apache CloudStack Administration Documentation package.
+# FIRST AUTHOR <EM...@ADDRESS>, YEAR.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: Apache CloudStack Administration Documentation 4\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2014-06-30 12:52+0200\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EM...@ADDRESS>\n"
+"Language-Team: LANGUAGE <LL...@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#: ../../hosts.rst:18
+# d162d1d06fd7403885aaa50b51be64cf
+msgid "Working with Hosts"
+msgstr ""
+
+#: ../../hosts.rst:21
+# 6c9e070451664a89a2bab7d9dcb4892e
+msgid "Adding Hosts"
+msgstr ""
+
+#: ../../hosts.rst:23
+# 0fea464db7a843f6930b135daf0f6eef
+msgid "Additional hosts can be added at any time to provide more capacity for guest VMs. For requirements and instructions, see `“Adding a Host” <http://docs.cloudstack.apache.org/projects/cloudstack-installation/en/latest/configuration.html#adding-a-host>`_."
+msgstr ""
+
+#: ../../hosts.rst:29
+# 8d309023c45240b78a9ddce49978e18c
+msgid "Scheduled Maintenance and Maintenance Mode for Hosts"
+msgstr ""
+
+#: ../../hosts.rst:31
+# 7a2b019ac10a47c39de133fdc1a06f3d
+msgid "You can place a host into maintenance mode. When maintenance mode is activated, the host becomes unavailable to receive new guest VMs, and the guest VMs already running on the host are seamlessly migrated to another host not in maintenance mode. This migration uses live migration technology and does not interrupt the execution of the guest."
+msgstr ""
+
+#: ../../hosts.rst:39
+# af2fbe9bb8ff4ab29c19fbb7dc7d6a2b
+msgid "vCenter and Maintenance Mode"
+msgstr ""
+
+#: ../../hosts.rst:41
+# d2d9b481634d47499c874f1781439746
+msgid "To enter maintenance mode on a vCenter host, both vCenter and CloudStack must be used in concert. CloudStack and vCenter have separate maintenance modes that work closely together."
+msgstr ""
+
+#: ../../hosts.rst:45
+# 1757e266dc494d81be5c3b51608b8507
+msgid "Place the host into CloudStack's \"scheduled maintenance\" mode. This does not invoke the vCenter maintenance mode, but only causes VMs to be migrated off the host"
+msgstr ""
+
+#: ../../hosts.rst:49
+# d96d3c3231d445ffbe5379d2f572a864
+msgid "When the CloudStack maintenance mode is requested, the host first moves into the Prepare for Maintenance state. In this state it cannot be the target of new guest VM starts. Then all VMs will be migrated off the server. Live migration will be used to move VMs off the host. This allows the guests to be migrated to other hosts with no disruption to the guests. After this migration is completed, the host will enter the Ready for Maintenance mode."
+msgstr ""
+
+#: ../../hosts.rst:57
+# a0302fba3abb4768b9ea6456150d1e34
+msgid "Wait for the \"Ready for Maintenance\" indicator to appear in the UI."
+msgstr ""
+
+#: ../../hosts.rst:59
+# bb2fe5471107450db78672f18f6c459b
+msgid "Now use vCenter to perform whatever actions are necessary to maintain the host. During this time, the host cannot be the target of new VM allocations."
+msgstr ""
+
+#: ../../hosts.rst:63
+# 465e081898184a07a0da7751a1b9540b
+msgid "When the maintenance tasks are complete, take the host out of maintenance mode as follows:"
+msgstr ""
+
+#: ../../hosts.rst:66
+# d513b1610d3f4e3c94c36672598225ef
+msgid "First use vCenter to exit the vCenter maintenance mode."
+msgstr ""
+
+#: ../../hosts.rst:68
+# 20604374352a49e78c96fc359907798b
+msgid "This makes the host ready for CloudStack to reactivate it."
+msgstr ""
+
+#: ../../hosts.rst:70
+# 268a4bfa21584498b9c29213e959d532
+msgid "Then use CloudStack's administrator UI to cancel the CloudStack maintenance mode"
+msgstr ""
+
+#: ../../hosts.rst:73
+# 473e00df4c58462d9df612fdba5c4996
+msgid "When the host comes back online, the VMs that were migrated off of it may be migrated back to it manually and new VMs can be added."
+msgstr ""
+
+#: ../../hosts.rst:78
+# 8026febd757948bdb38b4f85cbd4c425
+msgid "XenServer and Maintenance Mode"
+msgstr ""
+
+#: ../../hosts.rst:80
+# 38555be75efd4fed91c3479a883493d1
+msgid "For XenServer, you can take a server offline temporarily by using the Maintenance Mode feature in XenCenter. When you place a server into Maintenance Mode, all running VMs are automatically migrated from it to another host in the same pool. If the server is the pool master, a new master will also be selected for the pool. While a server is Maintenance Mode, you cannot create or start any VMs on it."
+msgstr ""
+
+#: ../../hosts.rst:87
+# 456e5e6e17bf41909c0b487227d097cd
+msgid "**To place a server in Maintenance Mode:**"
+msgstr ""
+
+#: ../../hosts.rst:89
+#: ../../hosts.rst:104
+# 5de27d0060754518bf21cd3ed27ed05a
+# 568c45e59b4f4b2294d24752311a5022
+msgid "In the Resources pane, select the server, then do one of the following:"
+msgstr ""
+
+#: ../../hosts.rst:92
+# a31b8242b89b4b24a48e8d242ed46718
+msgid "Right-click, then click Enter Maintenance Mode on the shortcut menu."
+msgstr ""
+
+#: ../../hosts.rst:95
+# 1e90893580c44442be56fd686ba4aab4
+msgid "On the Server menu, click Enter Maintenance Mode."
+msgstr ""
+
+#: ../../hosts.rst:97
+# 95cf013b55004f2486b693b9a9bdb52d
+msgid "Click Enter Maintenance Mode."
+msgstr ""
+
+#: ../../hosts.rst:99
+# e9120c5408d94ba89b65157b49de36ae
+msgid "The server's status in the Resources pane shows when all running VMs have been successfully migrated off the server."
+msgstr ""
+
+#: ../../hosts.rst:102
+# c8ae2b6b96814aa8a04dc2ceebbacabb
+msgid "**To take a server out of Maintenance Mode:**"
+msgstr ""
+
+#: ../../hosts.rst:107
+# ae539b7f53ce42e8b161a38c897302a8
+msgid "Right-click, then click Exit Maintenance Mode on the shortcut menu."
+msgstr ""
+
+#: ../../hosts.rst:110
+# ee115cfaf80446f49c0e9fae828c783e
+msgid "On the Server menu, click Exit Maintenance Mode."
+msgstr ""
+
+#: ../../hosts.rst:112
+# 7edbfea17cdb4c4a85766a3d46ccf8da
+msgid "Click Exit Maintenance Mode."
+msgstr ""
+
+#: ../../hosts.rst:116
+# e6edc76480294c5faf6518aaf5f6aacb
+msgid "Disabling and Enabling Zones, Pods, and Clusters"
+msgstr ""
+
+#: ../../hosts.rst:118
+# 144624e6273f4b5c94ed3f88c8fc95e3
+msgid "You can enable or disable a zone, pod, or cluster without permanently removing it from the cloud. This is useful for maintenance or when there are problems that make a portion of the cloud infrastructure unreliable. No new allocations will be made to a disabled zone, pod, or cluster until its state is returned to Enabled. When a zone, pod, or cluster is first added to the cloud, it is Disabled by default."
+msgstr ""
+
+#: ../../hosts.rst:125
+# 9fbfab10c6be45a3bd2f6c231c6737bb
+msgid "To disable and enable a zone, pod, or cluster:"
+msgstr ""
+
+#: ../../hosts.rst:127
+# 71e22a46ce644865b910006aaa048a8d
+msgid "Log in to the CloudStack UI as administrator"
+msgstr ""
+
+#: ../../hosts.rst:129
+#: ../../hosts.rst:404
+# 50c0cd124fa643fdbbc561152e0dbabf
+# e16a19456eb441b4ab3cf57ec846a391
+msgid "In the left navigation bar, click Infrastructure."
+msgstr ""
+
+#: ../../hosts.rst:131
+# 11fd25d319484ab2b87f09c842be5134
+msgid "In Zones, click View More."
+msgstr ""
+
+#: ../../hosts.rst:133
+# c9caf60acf104601bc0f0f946d22b0c5
+msgid "If you are disabling or enabling a zone, find the name of the zone in the list, and click the Enable/Disable button. |enable-disable.png|"
+msgstr ""
+
+#: ../../hosts.rst:136
+# 222f496a2d1e456589a79442f4ed34a5
+msgid "If you are disabling or enabling a pod or cluster, click the name of the zone that contains the pod or cluster."
+msgstr ""
+
+#: ../../hosts.rst:139
+# 8de91492f6c848dca361c3822956148a
+msgid "Click the Compute tab."
+msgstr ""
+
+#: ../../hosts.rst:141
+# 260854995dc747e8b0224b78525f9646
+msgid "In the Pods or Clusters node of the diagram, click View All."
+msgstr ""
+
+#: ../../hosts.rst:143
+# 5496ff56c1c74d689c2d2453c38b4708
+msgid "Click the pod or cluster name in the list."
+msgstr ""
+
+#: ../../hosts.rst:145
+# 893e62d5abbf47a38a0dd2c1a53d6a5a
+msgid "Click the Enable/Disable button. |enable-disable.png|"
+msgstr ""
+
+#: ../../hosts.rst:149
+# 8f3d3ce8e0c64e67aea7a02d485fb245
+msgid "Removing Hosts"
+msgstr ""
+
+#: ../../hosts.rst:151
+# 984b62f5ee574b5fa2921a9c51086739
+msgid "Hosts can be removed from the cloud as needed. The procedure to remove a host depends on the hypervisor type."
+msgstr ""
+
+#: ../../hosts.rst:156
+# 65240cc22f554f09bdc03200b95bd05d
+msgid "Removing XenServer and KVM Hosts"
+msgstr ""
+
+#: ../../hosts.rst:158
+# 879cec7da3564798aa9e0d864809678d
+msgid "A node cannot be removed from a cluster until it has been placed in maintenance mode. This will ensure that all of the VMs on it have been migrated to other Hosts. To remove a Host from the cloud:"
+msgstr ""
+
+#: ../../hosts.rst:162
+# 7b965bf8884a4bcba98b12aab945722c
+msgid "Place the node in maintenance mode."
+msgstr ""
+
+#: ../../hosts.rst:164
+# 1301a77070374e238eb438818854da08
+msgid "See `“Scheduled Maintenance and Maintenance Mode for Hosts” <#scheduled-maintenance-and-maintenance-mode-for-hosts>`_."
+msgstr ""
+
+#: ../../hosts.rst:167
+# 6cb63d9356e643f1b3e032a8056a89ee
+msgid "For KVM, stop the cloud-agent service."
+msgstr ""
+
+#: ../../hosts.rst:169
+# 3a90c7e2a9224f36b01d73a1df4cd39c
+msgid "Use the UI option to remove the node."
+msgstr ""
+
+#: ../../hosts.rst:171
+# 400a182ceace4cef87ffe6c731ea45cd
+msgid "Then you may power down the Host, re-use its IP address, re-install it, etc"
+msgstr ""
+
+#: ../../hosts.rst:176
+# b9297a05564a41f8aa6995f8f1e2265a
+msgid "Removing vSphere Hosts"
+msgstr ""
+
+#: ../../hosts.rst:178
+# c32ebbedc8304707ab76b57248d80fee
+msgid "To remove this type of host, first place it in maintenance mode, as described in `“Scheduled Maintenance and Maintenance Mode for Hosts” <#scheduled-maintenance-and-maintenance-mode-for-hosts>`_. Then use CloudStack to remove the host. CloudStack will not direct commands to a host that has been removed using CloudStack. However, the host may still exist in the vCenter cluster."
+msgstr ""
+
+#: ../../hosts.rst:187
+# dd4d1c612fb44dc195061dd566beec5e
+msgid "Re-Installing Hosts"
+msgstr ""
+
+#: ../../hosts.rst:189
+# 0ee9288a566b4631b2e8f680cfbe5b47
+msgid "You can re-install a host after placing it in maintenance mode and then removing it. If a host is down and cannot be placed in maintenance mode, it should still be removed before the re-install."
+msgstr ""
+
+#: ../../hosts.rst:195
+# c85fb73c99e34c10b3289143d58b305b
+msgid "Maintaining Hypervisors on Hosts"
+msgstr ""
+
+#: ../../hosts.rst:197
+# af548f5aa95e4755a881574a77d625fd
+msgid "When running hypervisor software on hosts, be sure all the hotfixes provided by the hypervisor vendor are applied. Track the release of hypervisor patches through your hypervisor vendor’s support channel, and apply patches as soon as possible after they are released. CloudStack will not track or notify you of required hypervisor patches. It is essential that your hosts are completely up to date with the provided hypervisor patches. The hypervisor vendor is likely to refuse to supp [...]
+msgstr ""
+
+#: ../../hosts.rst:207
+# fb13ff2e1e1c478e8ee99dbb7a71c69d
+msgid "The lack of up-do-date hotfixes can lead to data corruption and lost VMs."
+msgstr ""
+
+#: ../../hosts.rst:209
+# 0132d3f953a446e7af2712c1f7f204d9
+msgid "(XenServer) For more information, see `Highly Recommended Hotfixes for XenServer in the CloudStack Knowledge Base <http://docs.cloudstack.org/Knowledge_Base/Possible_VM_corruption_if_XenServer_Hotfix_is_not_Applied/Highly_Recommended_Hotfixes_for_XenServer_5.6_SP2>`_."
+msgstr ""
+
+#: ../../hosts.rst:215
+# a2b8576f632f48e8b6556fe7958a2b4e
+msgid "Changing Host Password"
+msgstr ""
+
+#: ../../hosts.rst:217
+# 026b9758a8234d5d82e1fd3c20d9f9d6
+msgid "The password for a XenServer Node, KVM Node, or vSphere Node may be changed in the database. Note that all Nodes in a Cluster must have the same password."
+msgstr ""
+
+#: ../../hosts.rst:221
+# d662651348254d968559ee61ec677c9d
+msgid "To change a Node's password:"
+msgstr ""
+
+#: ../../hosts.rst:223
+# eac8c72d0110440e8d47f458d4dfa691
+msgid "Identify all hosts in the cluster."
+msgstr ""
+
+#: ../../hosts.rst:225
+# 6c429aa99fc44f4e85ed4eda61090335
+msgid "Change the password on all hosts in the cluster. Now the password for the host and the password known to CloudStack will not match. Operations on the cluster will fail until the two passwords match."
+msgstr ""
+
+#: ../../hosts.rst:229
+# bd29f4605f0b40a9822294fd0cba68e4
+msgid "Get the list of host IDs for the host in the cluster where you are changing the password. You will need to access the database to determine these host IDs. For each hostname \"h\" (or vSphere cluster) that you are changing the password for, execute:"
+msgstr ""
+
+#: ../../hosts.rst:238
+# ae93d4bde54f48ef9b96126a36220883
+msgid "This should return a single ID. Record the set of such IDs for these hosts."
+msgstr ""
+
+#: ../../hosts.rst:241
+# 6e33a985c6204813a3beec13959e029a
+msgid "Update the passwords for the host in the database. In this example, we change the passwords for hosts with IDs 5, 10, and 12 to \"password\"."
+msgstr ""
+
+#: ../../hosts.rst:251
+# 36d8dc7ed9b3447a819222bfb445bd10
+msgid "Over-Provisioning and Service Offering Limits"
+msgstr ""
+
+#: ../../hosts.rst:253
+# 3e5ec1fcb0cf49fda1383c022d23de87
+msgid "(Supported for XenServer, KVM, and VMware)"
+msgstr ""
+
+#: ../../hosts.rst:255
+# 3633dc63fade45ad8b1bc222bb9ad425
+msgid "CPU and memory (RAM) over-provisioning factors can be set for each cluster to change the number of VMs that can run on each host in the cluster. This helps optimize the use of resources. By increasing the over-provisioning ratio, more resource capacity will be used. If the ratio is set to 1, no over-provisioning is done."
+msgstr ""
+
+#: ../../hosts.rst:261
+# 43467fc7868049cab2d4374ff0094af1
+msgid "The administrator can also set global default over-provisioning ratios in the cpu.overprovisioning.factor and mem.overprovisioning.factor global configuration variables. The default value of these variables is 1: over-provisioning is turned off by default."
+msgstr ""
+
+#: ../../hosts.rst:266
+# 253e39db71ed47619ec617fb7a5397ac
+msgid "Over-provisioning ratios are dynamically substituted in CloudStack's capacity calculations. For example:"
+msgstr ""
+
+#: ../../hosts.rst:269
+# 48cbfebf2e804785ba7f9631cb010778
+msgid "Capacity = 2 GB Over-provisioning factor = 2 Capacity after over-provisioning = 4 GB"
+msgstr ""
+
+#: ../../hosts.rst:273
+# af111e47b7cc4e53825770d523defc61
+msgid "With this configuration, suppose you deploy 3 VMs of 1 GB each:"
+msgstr ""
+
+#: ../../hosts.rst:275
+# 851386252faa45d69618b89e2ff7ba8e
+msgid "Used = 3 GB Free = 1 GB"
+msgstr ""
+
+#: ../../hosts.rst:278
+# fdd299fb9bed44d696ed49d97cd8779d
+msgid "The administrator can specify a memory over-provisioning ratio, and can specify both CPU and memory over-provisioning ratios on a per-cluster basis."
+msgstr ""
+
+#: ../../hosts.rst:282
+# 13239c1da0164d2e88a9275d8083e8aa
+msgid "In any given cloud, the optimum number of VMs for each host is affected by such things as the hypervisor, storage, and hardware configuration. These may be different for each cluster in the same cloud. A single global over-provisioning setting can not provide the best utilization for all the different clusters in the cloud. It has to be set for the lowest common denominator. The per-cluster setting provides a finer granularity for better utilization of resources, no matter where t [...]
+msgstr ""
+
+#: ../../hosts.rst:291
+# 14bb9814011f4bb6972aeb18939b2e6c
+msgid "The overprovisioning settings can be used along with dedicated resources (assigning a specific cluster to an account) to effectively offer different levels of service to different accounts. For example, an account paying for a more expensive level of service could be assigned to a dedicated cluster with an over-provisioning ratio of 1, and a lower-paying account to a cluster with a ratio of 2."
+msgstr ""
+
+#: ../../hosts.rst:298
+# a04ae50db280409bacc1c0752456eb1b
+msgid "When a new host is added to a cluster, CloudStack will assume the host has the capability to perform the CPU and RAM over-provisioning which is configured for that cluster. It is up to the administrator to be sure the host is actually suitable for the level of over-provisioning which has been set."
+msgstr ""
+
+#: ../../hosts.rst:306
+# bc9d355b0e014b5ab9fd367c9e80ab24
+msgid "Limitations on Over-Provisioning in XenServer and KVM"
+msgstr ""
+
+#: ../../hosts.rst:308
+#: ../../hosts.rst:416
+# c556b8018bbd4fee9f244adf40b4f51d
+# 536dc98cafb74355b90a4bea9be01f99
+msgid "In XenServer, due to a constraint of this hypervisor, you can not use an over-provisioning factor greater than 4."
+msgstr ""
+
+#: ../../hosts.rst:311
+# a9dd662370ca407596ca9fa0b313a3af
+msgid "The KVM hypervisor can not manage memory allocation to VMs dynamically. CloudStack sets the minimum and maximum amount of memory that a VM can use. The hypervisor adjusts the memory within the set limits based on the memory contention."
+msgstr ""
+
+#: ../../hosts.rst:318
+# 4eb1b9a8ad484a8fa8cb381ce6b52eb2
+msgid "Requirements for Over-Provisioning"
+msgstr ""
+
+#: ../../hosts.rst:320
+# b5394f77c74e479980f2f996e9f81251
+msgid "Several prerequisites are required in order for over-provisioning to function properly. The feature is dependent on the OS type, hypervisor capabilities, and certain scripts. It is the administrator's responsibility to ensure that these requirements are met."
+msgstr ""
+
+#: ../../hosts.rst:327
+# 4fc500a083b4403998ada5877b9d0de0
+msgid "Balloon Driver"
+msgstr ""
+
+#: ../../hosts.rst:329
+# 9e1eb0f5b30a4a9cbebcf773c16bf440
+msgid "All VMs should have a balloon driver installed in them. The hypervisor communicates with the balloon driver to free up and make the memory available to a VM."
+msgstr ""
+
+#: ../../hosts.rst:335
+#: ../../hosts.rst:365
+# 588dfd76655d44b999fcc554493271ee
+# 876a75ef59a549349b25f46f2f3fc8bf
+msgid "XenServer"
+msgstr ""
+
+#: ../../hosts.rst:337
+# cc2308bc95464b93a3dc5631c6edb411
+msgid "The balloon driver can be found as a part of xen pv or PVHVM drivers. The xen pvhvm drivers are included in upstream linux kernels 2.6.36+."
+msgstr ""
+
+#: ../../hosts.rst:342
+# db7f94775ac3401c8e7da496601ce4d7
+msgid "VMware"
+msgstr ""
+
+#: ../../hosts.rst:344
+# db5f8890af6c435aa86e4c6106f0d83e
+msgid "The balloon driver can be found as a part of the VMware tools. All the VMs that are deployed in a over-provisioned cluster should have the VMware tools installed."
+msgstr ""
+
+#: ../../hosts.rst:350
+# e051f09fe032421881651a264ec5562c
+msgid "KVM"
+msgstr ""
+
+#: ../../hosts.rst:352
+# 9c51a6068b774e919cd552b525963bef
+msgid "All VMs are required to support the virtio drivers. These drivers are installed in all Linux kernel versions 2.6.25 and greater. The administrator must set CONFIG\\_VIRTIO\\_BALLOON=y in the virtio configuration."
+msgstr ""
+
+#: ../../hosts.rst:359
+# c8150c4e5af743bd8897bbd116c538d7
+msgid "Hypervisor capabilities"
+msgstr ""
+
+#: ../../hosts.rst:361
+# efc1f0769cdf44d0aee285aed27c7e0f
+msgid "The hypervisor must be capable of using the memory ballooning."
+msgstr ""
+
+#: ../../hosts.rst:367
+# 8b282cb5f7914088be3b38b87b604492
+msgid "The DMC (Dynamic Memory Control) capability of the hypervisor should be enabled. Only XenServer Advanced and above versions have this feature."
+msgstr ""
+
+#: ../../hosts.rst:372
+# 11e7b221209c4b97ab044dbbb6c53b0e
+msgid "VMware, KVM"
+msgstr ""
+
+#: ../../hosts.rst:374
+# c289bebec04c474c9497ce81216e04f1
+msgid "Memory ballooning is supported by default."
+msgstr ""
+
+#: ../../hosts.rst:378
+# fd73c49bd922450fb7a771ebb8586d6d
+msgid "Setting Over-Provisioning Ratios"
+msgstr ""
+
+#: ../../hosts.rst:380
+# 7d8bbd43174f499a98270e1aad9301bd
+msgid "There are two ways the root admin can set CPU and RAM over-provisioning ratios. First, the global configuration settings cpu.overprovisioning.factor and mem.overprovisioning.factor will be applied when a new cluster is created. Later, the ratios can be modified for an existing cluster."
+msgstr ""
+
+#: ../../hosts.rst:386
+# 6930197d999a4c1bb3e8bca13bb10c00
+msgid "Only VMs deployed after the change are affected by the new setting. If you want VMs deployed before the change to adopt the new over-provisioning ratio, you must stop and restart the VMs. When this is done, CloudStack recalculates or scales the used and reserved capacities based on the new over-provisioning ratios, to ensure that CloudStack is correctly tracking the amount of free capacity."
+msgstr ""
+
+#: ../../hosts.rst:394
+# fe4660151e234650980661b9975d4c77
+msgid "It is safer not to deploy additional new VMs while the capacity recalculation is underway, in case the new values for available capacity are not high enough to accommodate the new VMs. Just wait for the new used/available values to become available, to be sure there is room for all the new VMs you want."
+msgstr ""
+
+#: ../../hosts.rst:400
+# 443b0ee66d0b40bdad6e11ac6c4eb123
+msgid "To change the over-provisioning ratios for an existing cluster:"
+msgstr ""
+
+#: ../../hosts.rst:402
+# b796b807352f4f8285fca177e9417577
+msgid "Log in as administrator to the CloudStack UI."
+msgstr ""
+
+#: ../../hosts.rst:406
+# 450e03bbb9974112bec16a0dca62c829
+msgid "Under Clusters, click View All."
+msgstr ""
+
+#: ../../hosts.rst:408
+# dc9598fec6f74c74a82c2311ff962b5d
+msgid "Select the cluster you want to work with, and click the Edit button."
+msgstr ""
+
+#: ../../hosts.rst:410
+# 4574765089c64df0a53ffd4b0d9052a0
+msgid "Fill in your desired over-provisioning multipliers in the fields CPU overcommit ratio and RAM overcommit ratio. The value which is intially shown in these fields is the default value inherited from the global configuration settings."
+msgstr ""
+
+#: ../../hosts.rst:421
+# 2652eabbfcd64f92bab0644f7cddd8d6
+msgid "Service Offering Limits and Over-Provisioning"
+msgstr ""
+
+#: ../../hosts.rst:423
+# d88ad9813f6448ec9277039383ab3f86
+msgid "Service offering limits (e.g. 1 GHz, 1 core) are strictly enforced for core count. For example, a guest with a service offering of one core will have only one core available to it regardless of other activity on the Host."
+msgstr ""
+
+#: ../../hosts.rst:428
+# 0a5fa05e882e493f8d41201840eb0cd9
+msgid "Service offering limits for gigahertz are enforced only in the presence of contention for CPU resources. For example, suppose that a guest was created with a service offering of 1 GHz on a Host that has 2 GHz cores, and that guest is the only guest running on the Host. The guest will have the full 2 GHz available to it. When multiple guests are attempting to use the CPU a weighting factor is used to schedule CPU resources. The weight is based on the clock speed in the service offe [...]
+msgstr ""
+
+#: ../../hosts.rst:442
+# 86b75c2fbf034662ac3133fe63acefea
+msgid "VLAN Provisioning"
+msgstr ""
+
+#: ../../hosts.rst:444
+# 9d66a1eb7d4d4d88818d5d5d00bb285a
+msgid "CloudStack automatically creates and destroys interfaces bridged to VLANs on the hosts. In general the administrator does not need to manage this process."
+msgstr ""
+
+#: ../../hosts.rst:448
+# 7cfe38c7368a44d1b920f68fbb7e2b5e
+msgid "CloudStack manages VLANs differently based on hypervisor type. For XenServer or KVM, the VLANs are created on only the hosts where they will be used and then they are destroyed when all guests that require them have been terminated or moved to another host."
+msgstr ""
+
+#: ../../hosts.rst:453
+# a681bdc643fc41a49688c3a833dce9ac
+msgid "For vSphere the VLANs are provisioned on all hosts in the cluster even if there is no guest running on a particular Host that requires the VLAN. This allows the administrator to perform live migration and other functions in vCenter without having to create the VLAN on the destination Host. Additionally, the VLANs are not removed from the Hosts when they are no longer needed."
+msgstr ""
+
+#: ../../hosts.rst:460
+# 162b7ae68b2d41db83c3bc6d32e86e6b
+msgid "You can use the same VLANs on different physical networks provided that each physical network has its own underlying layer-2 infrastructure, such as switches. For example, you can specify VLAN range 500 to 1000 while deploying physical networks A and B in an Advanced zone setup. This capability allows you to set up an additional layer-2 physical infrastructure on a different physical NIC and use the same set of VLANs if you run out of VLANs. Another advantage is that you can use t [...]
+msgstr ""
+
+#: ../../hosts.rst:472
+# d4316f84d139424ab25c6fb9292b2840
+msgid "VLAN Allocation Example"
+msgstr ""
+
+#: ../../hosts.rst:474
+# ea6edc6b827c4791a53ea10997662dae
+msgid "VLANs are required for public and guest traffic. The following is an example of a VLAN allocation scheme:"
+msgstr ""
+
+#: ../../hosts.rst:478
+# 558c3d372c85421390186a570da26dee
+msgid "VLAN IDs"
+msgstr ""
+
+#: ../../hosts.rst:478
+# b6c7ef27f668454dbb5adb9a9c190c98
+msgid "Traffic type"
+msgstr ""
+
+#: ../../hosts.rst:478
+# 2dc30077851f4826beeaeb3c808e6452
+msgid "Scope"
+msgstr ""
+
+#: ../../hosts.rst:480
+# 46e966a312a047cfa77c7292aaba1fdb
+msgid "less than 500"
+msgstr ""
+
+#: ../../hosts.rst:480
+# c6ffd280911a498f99904379cc538935
+msgid "Management traffic."
+msgstr ""
+
+#: ../../hosts.rst:480
+# bb76ee312d884069ac0a101cfc2680d2
+msgid "Reserved for administrative purposes.  CloudStack software can access this, hypervisors, system VMs."
+msgstr ""
+
+#: ../../hosts.rst:481
+# 1307c25d94c447a08ebf7b1f47d76fa7
+msgid "500-599"
+msgstr ""
+
+#: ../../hosts.rst:481
+# fb79eefe00ad444eaf660e4c6c7571b7
+msgid "VLAN carrying public traffic."
+msgstr ""
+
+#: ../../hosts.rst:481
+# 0c7d0d0d68c94f5f889f1e32dcb564cb
+msgid "CloudStack accounts."
+msgstr ""
+
+#: ../../hosts.rst:482
+# 9ab975c827154ebd84ab2f50936736b8
+msgid "600-799"
+msgstr ""
+
+#: ../../hosts.rst:482
+#: ../../hosts.rst:483
+# e33f1854a40043ed9d323fa1f1a3519d
+# 1dfa7469eec44ea6b03b34b9c6f7504e
+msgid "VLANs carrying guest traffic."
+msgstr ""
+
+#: ../../hosts.rst:482
+# e10058e68df14ced9dda12d02876f4c4
+msgid "CloudStack accounts. Account-specific VLAN is chosen from this pool."
+msgstr ""
+
+#: ../../hosts.rst:483
+# 26028e0cc17c46ceae4008c85730b970
+msgid "800-899"
+msgstr ""
+
+#: ../../hosts.rst:483
+# a894ab0d32654721aa09284c57bbabc4
+msgid "CloudStack accounts. Account-specific VLAN chosen by CloudStack admin to assign to that account."
+msgstr ""
+
+#: ../../hosts.rst:484
+# 4a297ddc517048fab79c4a44c5ad0b99
+msgid "900-999"
+msgstr ""
+
+#: ../../hosts.rst:484
+# 404678aaa64349f8924466d04c12db32
+msgid "VLAN carrying guest traffic"
+msgstr ""
+
+#: ../../hosts.rst:484
+# 185277c2c47d409cb9ec68e3f03ceddc
+msgid "CloudStack accounts. Can be scoped by project, domain, or all accounts."
+msgstr ""
+
+#: ../../hosts.rst:485
+# 5032da4e90be448f905a4ee48df7d8ed
+msgid "greater than 1000"
+msgstr ""
+
+#: ../../hosts.rst:485
+# af16d28d60df4d84b3951c37a78f02bc
+msgid "Reserved for future use"
+msgstr ""
+
+#: ../../hosts.rst:490
+# ef44b9e8dc084564a01254fc196c3b9e
+msgid "Adding Non Contiguous VLAN Ranges"
+msgstr ""
+
+#: ../../hosts.rst:492
+# 5b73c96b899144be9a84d12c7ed11d55
+msgid "CloudStack provides you with the flexibility to add non contiguous VLAN ranges to your network. The administrator can either update an existing VLAN range or add multiple non contiguous VLAN ranges while creating a zone. You can also use the UpdatephysicalNetwork API to extend the VLAN range."
+msgstr ""
+
+#: ../../hosts.rst:498
+# 957172517a6845a3915b26e7b95812d0
+msgid "Log in to the CloudStack UI as an administrator or end user."
+msgstr ""
+
+#: ../../hosts.rst:500
+# cb713605543d4f8eb0ffd5bec494839d
+msgid "Ensure that the VLAN range does not already exist."
+msgstr ""
+
+#: ../../hosts.rst:502
+# 6543749bf38741be83173b69828b1f49
+msgid "In the left navigation, choose Infrastructure."
+msgstr ""
+
+#: ../../hosts.rst:504
+# 7bd96bd6e7fd4c94bd7be28295bd46de
+msgid "On Zones, click View More, then click the zone to which you want to work with."
+msgstr ""
+
+#: ../../hosts.rst:507
+# 29ea322032104b06880f1204aa29a145
+msgid "Click Physical Network."
+msgstr ""
+
+#: ../../hosts.rst:509
+# a6e5a25d6929406594577a6b3f074454
+msgid "In the Guest node of the diagram, click Configure."
+msgstr ""
+
+#: ../../hosts.rst:511
+# b85881c793b045978846d5eb97408757
+msgid "Click Edit |edit-icon.png|."
+msgstr ""
+
+#: ../../hosts.rst:513
+# 061af0a695ad4e1abcd195287ee6e0ef
+msgid "The VLAN Ranges field now is editable."
+msgstr ""
+
+#: ../../hosts.rst:515
+# 131fadb281474dc597e34d3fe0d6d444
+msgid "Specify the start and end of the VLAN range in comma-separated list."
+msgstr ""
+
+#: ../../hosts.rst:517
+# aaf0146792d5487297eff314b521c053
+msgid "Specify all the VLANs you want to use, VLANs not specified will be removed if you are adding new ranges to the existing list."
+msgstr ""
+
+#: ../../hosts.rst:520
+# d7cd1af070644a71ae33b79fbc724b87
+msgid "Click Apply."
+msgstr ""
+
+#: ../../hosts.rst:524
+# 9685350eac754d8c889dc8da19292529
+msgid "Assigning VLANs to Isolated Networks"
+msgstr ""
+
+#: ../../hosts.rst:526
+# 31001908f2bd40018f7b77a9001e50c7
+msgid "CloudStack provides you the ability to control VLAN assignment to Isolated networks. As a Root admin, you can assign a VLAN ID when a network is created, just the way it's done for Shared networks."
+msgstr ""
+
+#: ../../hosts.rst:530
+# 47af367fd0e74e9c98c07d5fd93d9a6a
+msgid "The former behaviour also is supported — VLAN is randomly allocated to a network from the VNET range of the physical network when the network turns to Implemented state. The VLAN is released back to the VNET pool when the network shuts down as a part of the Network Garbage Collection. The VLAN can be re-used either by the same network when it is implemented again, or by any other network. On each subsequent implementation of a network, a new VLAN can be assigned."
+msgstr ""
+
+#: ../../hosts.rst:538
+# 1ba6d80370024ab596ffd9d4ae6294cc
+msgid "Only the Root admin can assign VLANs because the regular users or domain admin are not aware of the physical network topology. They cannot even view what VLAN is assigned to a network."
+msgstr ""
+
+#: ../../hosts.rst:542
+# f8d82f2f80da4f4fbdef3b4308538511
+msgid "To enable you to assign VLANs to Isolated networks,"
+msgstr ""
+
+#: ../../hosts.rst:544
+# 51e781fd8ac2474f896774fe185ff585
+msgid "Create a network offering by specifying the following:"
+msgstr ""
+
+#: ../../hosts.rst:546
+# 38ae271a7f7f4855a4353c109d01d761
+msgid "**Guest Type**: Select Isolated."
+msgstr ""
+
+#: ../../hosts.rst:548
+# 136f37de7a6f4b1ead01c213603a4a47
+msgid "**Specify VLAN**: Select the option."
+msgstr ""
+
+#: ../../hosts.rst:550
+# ba4c14a8b3d94e1fbeccb6afd28ec4ad
+msgid "For more information, see the CloudStack Installation Guide."
+msgstr ""
+
+#: ../../hosts.rst:552
+# 42fbeadc772741cdb88549a149bef4c4
+msgid "Using this network offering, create a network."
+msgstr ""
+
+#: ../../hosts.rst:554
+# b08c9effb9bf43ecb0e42699daf88922
+msgid "You can create a VPC tier or an Isolated network."
+msgstr ""
+
+#: ../../hosts.rst:556
+# d1ae253e49f3473a9ee2ed29b8447270
+msgid "Specify the VLAN when you create the network."
+msgstr ""
+
+#: ../../hosts.rst:558
+# d4c5557c8994473ba6ca182dc7149c44
+msgid "When VLAN is specified, a CIDR and gateway are assigned to this network and the state is changed to Setup. In this state, the network will not be garbage collected."
+msgstr ""
+
+#: ../../hosts.rst:563
+# 89369b26917b4d54ad28290b37c59b53
+msgid "You cannot change a VLAN once it's assigned to the network. The VLAN remains with the network for its entire life cycle."
+msgstr ""
+
diff --git a/source/adminguide/locale/pot/index.pot b/source/adminguide/locale/pot/index.pot
new file mode 100644
index 0000000..8133094
--- /dev/null
+++ b/source/adminguide/locale/pot/index.pot
@@ -0,0 +1,128 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 
+# This file is distributed under the same license as the Apache CloudStack Administration Documentation package.
+# FIRST AUTHOR <EM...@ADDRESS>, YEAR.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: Apache CloudStack Administration Documentation 4\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2014-06-30 12:52+0200\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EM...@ADDRESS>\n"
+"Language-Team: LANGUAGE <LL...@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#: ../../index.rst:23
+# 84926a62ef4145eb8258fb18cc990020
+msgid "Welcome to CloudStack Administration Documentation"
+msgstr ""
+
+#: ../../index.rst:29
+# 17401d6f4fa445e288e17f050447db52
+msgid "We are in the process of changing documentation format as well as hosting mechanism. Please be patient with us as we migrate our entire documentation to this new setup."
+msgstr ""
+
+#: ../../index.rst:32
+# 3ed721b0cbc84d29b41f1f88c145794b
+msgid "This guide is aimed at Administrators of a CloudStack based Cloud, for Release Notes, Installation and General introduction to CloudStack see the following guides:"
+msgstr ""
+
+#: ../../index.rst:36
+# 6bdec416d5864e24a626b2a1672d12fc
+msgid "`Documentation Start <http://docs.cloudstack.apache.org>`_"
+msgstr ""
+
+#: ../../index.rst:38
+# 59647f13b4c6495bb231941872f8615c
+msgid "`Installation Guide <http://docs.cloudstack.apache.org/projects/cloudstack-installation>`_"
+msgstr ""
+
+#: ../../index.rst:40
+# 3cb4b38db39a4954baa74c5207e46806
+msgid "`Release Notes <http://docs.cloudstack.apache.org/projects/cloudstack-release-notes>`_"
+msgstr ""
+
+#: ../../index.rst:44
+# 62705a3d035f4c9894e165081f5341b0
+msgid "User Interface"
+msgstr ""
+
+#: ../../index.rst:53
+# 253ae3a9066e4b22aa50e77c73b69357
+msgid "Managing Accounts, Users and Domains"
+msgstr ""
+
+#: ../../index.rst:62
+# bb51dd2b7b6d4b6287d5b832dd1ef9f3
+msgid "Using Projects to Organize User Resources"
+msgstr ""
+
+#: ../../index.rst:70
+# fcbcd54779cb4d14b7c28ea8e525c2ff
+msgid "Service Offerings"
+msgstr ""
+
+#: ../../index.rst:79
+# 2fed4745955e4e73b1b3bd6c4664a015
+msgid "Setting up Networking for Users"
+msgstr ""
+
+#: ../../index.rst:88
+# 37cb22ac86ef4acb9c046bc1dc7f7de4
+msgid "Working with Virtual Machines"
+msgstr ""
+
+#: ../../index.rst:97
+# 625c8add441e4edeac86a1ec4f792cec
+msgid "Working with Templates"
+msgstr ""
+
+#: ../../index.rst:106
+# 7ad29a9c67c74560b24731372d219e23
+msgid "Working with Hosts"
+msgstr ""
+
+#: ../../index.rst:115
+# a3332c4666934361ad83c88e6946f7f7
+msgid "Working with Storage"
+msgstr ""
+
+#: ../../index.rst:124
+# f2f20fd23af44019b1f0578d399c9ecc
+msgid "Working with System Virtual Machines"
+msgstr ""
+
+#: ../../index.rst:133
+# 73fe247fe2a14cf08be624ae4f8d5926
+msgid "Working with Usage"
+msgstr ""
+
+#: ../../index.rst:142
+# 5d20c3a9b5124254a155ba5a519c85ca
+msgid "Managing Networks and Traffic"
+msgstr ""
+
+#: ../../index.rst:151
+# c591434a39994a6fa8546f4b1115eb07
+msgid "Managing the Cloud"
+msgstr ""
+
+#: ../../index.rst:160
+# 1ffdcf555b9a45d58d6a0e3b4d670037
+msgid "System Reliability and Availability"
+msgstr ""
+
+#: ../../index.rst:169
+# 8422886b2cfe4b9c9d2adf3afd86f37f
+msgid "Tuning"
+msgstr ""
+
+#: ../../index.rst:178
+# c05956039d98457abe5c11b6f7661b23
+msgid "Events and Troubleshooting"
+msgstr ""
+
diff --git a/source/adminguide/locale/pot/management.pot b/source/adminguide/locale/pot/management.pot
new file mode 100644
index 0000000..96ab7aa
--- /dev/null
+++ b/source/adminguide/locale/pot/management.pot
@@ -0,0 +1,458 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 
+# This file is distributed under the same license as the Apache CloudStack Administration Documentation package.
+# FIRST AUTHOR <EM...@ADDRESS>, YEAR.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: Apache CloudStack Administration Documentation 4\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2014-06-30 12:52+0200\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EM...@ADDRESS>\n"
+"Language-Team: LANGUAGE <LL...@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#: ../../management.rst:18
+# 36cc316d379647279da05d191cf9e9b5
+msgid "Managing the Cloud"
+msgstr ""
+
+#: ../../management.rst:21
+# 0dc09dfbe9e34a9cb51831005d8fc025
+msgid "Using Tags to Organize Resources in the Cloud"
+msgstr ""
+
+#: ../../management.rst:23
+# 3ead5d7ddceb4d98a278abeeed0683c2
+msgid "A tag is a key-value pair that stores metadata about a resource in the cloud. Tags are useful for categorizing resources. For example, you can tag a user VM with a value that indicates the user's city of residence. In this case, the key would be \"city\" and the value might be \"Toronto\" or \"Tokyo.\" You can then request CloudStack to find all resources that have a given tag; for example, VMs for users in a given city."
+msgstr ""
+
+#: ../../management.rst:30
+# 6388318fab6c44f58fd92b854f510717
+msgid "You can tag a user virtual machine, volume, snapshot, guest network, template, ISO, firewall rule, port forwarding rule, public IP address, security group, load balancer rule, project, VPC, network ACL, or static route. You can not tag a remote access VPN."
+msgstr ""
+
+#: ../../management.rst:35
+# 87e95cabe82f4b7f86c2cd1cc303b912
+msgid "You can work with tags through the UI or through the API commands createTags, deleteTags, and listTags. You can define multiple tags for each resource. There is no limit on the number of tags you can define. Each tag can be up to 255 characters long. Users can define tags on the resources they own, and administrators can define tags on any resources in the cloud."
+msgstr ""
+
+#: ../../management.rst:42
+# c2db56ab546245ec9d37ccf72573c16c
+msgid "An optional input parameter, \"tags,\" exists on many of the list\\* API commands. The following example shows how to use this new parameter to find all the volumes having tag region=canada OR tag city=Toronto:"
+msgstr ""
+
+#: ../../management.rst:55
+# 0d735394ca9f48f8a4ef3c5d0a25741d
+msgid "The following API commands have the \"tags\" input parameter:"
+msgstr ""
+
+#: ../../management.rst:57
+# 6d986331aa5d4971bab13111a8471d36
+msgid "listVirtualMachines"
+msgstr ""
+
+#: ../../management.rst:59
+# b0e2702f6aed49a8831ae5c2983a18c9
+msgid "listVolumes"
+msgstr ""
+
+#: ../../management.rst:61
+# 97c53594680a4cecb64e3f1a5ea2a2f3
+msgid "listSnapshots"
+msgstr ""
+
+#: ../../management.rst:63
+# 0217180a24604d579084142d07f11299
+msgid "listNetworks"
+msgstr ""
+
+#: ../../management.rst:65
+# dcf958a652304820818033fc441226e7
+msgid "listTemplates"
+msgstr ""
+
+#: ../../management.rst:67
+# 296660956a3b4ce5b02c4c7f1272e889
+msgid "listIsos"
+msgstr ""
+
+#: ../../management.rst:69
+# 69e88bee17394199a778180f3304fbf0
+msgid "listFirewallRules"
+msgstr ""
+
+#: ../../management.rst:71
+# 7954e7afc0334bc7bfcf16492195bb49
+msgid "listPortForwardingRules"
+msgstr ""
+
+#: ../../management.rst:73
+# d273e10141d84eecbdc74ec901700d11
+msgid "listPublicIpAddresses"
+msgstr ""
+
+#: ../../management.rst:75
+# b3e40262a34d4590bed84b8d5fc62798
+msgid "listSecurityGroups"
+msgstr ""
+
+#: ../../management.rst:77
+# e8f6e365e1da4b499d6b852d6c3e1162
+msgid "listLoadBalancerRules"
+msgstr ""
+
+#: ../../management.rst:79
+# 3c8faeeede5147fb911f022fd5858210
+msgid "listProjects"
+msgstr ""
+
+#: ../../management.rst:81
+# a9805315805e4d75b977c3428bcde48a
+msgid "listVPCs"
+msgstr ""
+
+#: ../../management.rst:83
+# bfab0c32d8364cd9a3e762e7992888f1
+msgid "listNetworkACLs"
+msgstr ""
+
+#: ../../management.rst:85
+# 46fab81fefa1469eb87698342b0f045e
+msgid "listStaticRoutes"
+msgstr ""
+
+#: ../../management.rst:89
+# 489808dcb1c9407cbe2bd271c02ce89a
+msgid "Reporting CPU Sockets"
+msgstr ""
+
+#: ../../management.rst:91
+# 7d8f4e987714451e9db1c9e749f8b1ca
+msgid "PRODUCT manages different types of hosts that contains one or more physical CPU sockets. CPU socket is considered as a unit of measure used for licensing and billing cloud infrastructure. PRODUCT provides both UI and API support to collect the CPU socket statistics for billing purpose. The Infrastructure tab has a new tab for CPU sockets. You can view the statistics for CPU sockets managed by PRODUCT, which in turn reflects the size of the cloud. The CPU Socket page will give you  [...]
+msgstr ""
+
+#: ../../management.rst:100
+# dec087784ccd48c49189c3f0ed1811a9
+msgid "Log in to the PRODUCT UI."
+msgstr ""
+
+#: ../../management.rst:102
+# 012d9d141d8745a48fd182b1cab1f8f1
+msgid "In the left navigation bar, click Infrastructure."
+msgstr ""
+
+#: ../../management.rst:104
+# 991d040f4ccc467f87019591608beea8
+msgid "On CPU Sockets, click View all."
+msgstr ""
+
+#: ../../management.rst:106
+# 1f3a30df3d8746f291bc00e761d59f3e
+msgid "The CPU Socket page is displayed. The page shows the number of hosts and CPU sockets based on hypervisor types."
+msgstr ""
+
+#: ../../management.rst:111
+# 3d662bf06abc42bd951d16844faada76
+msgid "Changing the Database Configuration"
+msgstr ""
+
+#: ../../management.rst:113
+# 638ca3cbc00844789edafb4eb0e60df5
+msgid "The CloudStack Management Server stores database configuration information (e.g., hostname, port, credentials) in the file ``/etc/cloudstack/management/db.properties``. To effect a change, edit this file on each Management Server, then restart the Management Server."
+msgstr ""
+
+#: ../../management.rst:119
+# a0530bddfe5a47a69ac27ef0a2c38a2e
+msgid "Changing the Database Password"
+msgstr ""
+
+#: ../../management.rst:121
+# 6ede044a32ac422baed2cd80afc2e114
+msgid "You may need to change the password for the MySQL account used by CloudStack. If so, you'll need to change the password in MySQL, and then add the encrypted password to ``/etc/cloudstack/management/db.properties``."
+msgstr ""
+
+#: ../../management.rst:126
+# 803fea7347b74457808913e8d34560e4
+msgid "Before changing the password, you'll need to stop CloudStack's management server and the usage engine if you've deployed that component."
+msgstr ""
+
+#: ../../management.rst:135
+# 83b051e006ce4a898817788447a54253
+msgid "Next, you'll update the password for the CloudStack user on the MySQL server."
+msgstr ""
+
+#: ../../management.rst:142
+# a6ed0f9a1e5f41d9883e8ab8e6ed7157
+msgid "At the MySQL shell, you'll change the password and flush privileges:"
+msgstr ""
+
+#: ../../management.rst:150
+# 5042ed8fa23b4aa6bf244fb7e8d21d0b
+msgid "The next step is to encrypt the password and copy the encrypted password to CloudStack's database configuration (``/etc/cloudstack/management/db.properties``)."
+msgstr ""
+
+#: ../../management.rst:160
+# 08fe5ba4a2844019b7c34948af80d3e9
+msgid "File encryption type"
+msgstr ""
+
+#: ../../management.rst:162
+# a985e48a20754561ae6daee44e6d79a8
+msgid "Note that this is for the file encryption type. If you're using the web encryption type then you'll use password=\"management\\_server\\_secret\\_key\""
+msgstr ""
+
+#: ../../management.rst:166
+# 41348185b9bc4aa59d47266350f37bea
+msgid "Now, you'll update ``/etc/cloudstack/management/db.properties`` with the new ciphertext. Open ``/etc/cloudstack/management/db.properties`` in a text editor, and update these parameters:"
+msgstr ""
+
+#: ../../management.rst:175
+# 3224048da0604d5e8ff7b22550451ce5
+msgid "After copying the new password over, you can now start CloudStack (and the usage engine, if necessary)."
+msgstr ""
+
+#: ../../management.rst:185
+# b42158e718f44c4ab881833d2dbc0929
+msgid "Administrator Alerts"
+msgstr ""
+
+#: ../../management.rst:187
+# f35a6a1c63244c84b73055d401027bf8
+msgid "The system provides alerts and events to help with the management of the cloud. Alerts are notices to an administrator, generally delivered by e-mail, notifying the administrator that an error has occurred in the cloud. Alert behavior is configurable."
+msgstr ""
+
+#: ../../management.rst:192
+# ff3195bd128540cca761c8b00697d461
+msgid "Events track all of the user and administrator actions in the cloud. For example, every guest VM start creates an associated event. Events are stored in the Management Server’s database."
+msgstr ""
+
+#: ../../management.rst:196
+# 6b6c7d267ebc4ecdba5787f75ed95d52
+msgid "Emails will be sent to administrators under the following circumstances:"
+msgstr ""
+
+#: ../../management.rst:198
+# 239b319d590244788e6be621087e695a
+msgid "The Management Server cluster runs low on CPU, memory, or storage resources"
+msgstr ""
+
+#: ../../management.rst:201
+# 11bbb0a3f5de4024ac7e944c1603e026
+msgid "The Management Server loses heartbeat from a Host for more than 3 minutes"
+msgstr ""
+
+#: ../../management.rst:204
+# f6a69a83f8bb45a193d273cbd63ac7bd
+msgid "The Host cluster runs low on CPU, memory, or storage resources"
+msgstr ""
+
+#: ../../management.rst:208
+# 267b4ae8b12e42d69f646aa22992388d
+msgid "Sending Alerts to External SNMP and Syslog Managers"
+msgstr ""
+
+#: ../../management.rst:210
+# 030acb1fc907414196ead65866a918b0
+msgid "In addition to showing administrator alerts on the Dashboard in the CloudStack UI and sending them in email, CloudStack can also send the same alerts to external SNMP or Syslog management software. This is useful if you prefer to use an SNMP or Syslog manager to monitor your cloud."
+msgstr ""
+
+#: ../../management.rst:216
+# ae64dcb892834822b7480195c2882a8c
+msgid "The alerts which can be sent are:"
+msgstr ""
+
+#: ../../management.rst:218
+# 814ff89fb6f444fc96a8b87a532bc28f
+msgid "The following is the list of alert type numbers. The current alerts can be found by calling listAlerts."
+msgstr ""
+
+#: ../../management.rst:330
+# cac2d1c9d3a34cb29f25fc81630f96dc
+msgid "You can also display the most up to date list by calling the API command ``listAlerts``."
+msgstr ""
+
+#: ../../management.rst:334
+# 0ead10e6a3664baf84b6199d70dfb243
+msgid "SNMP Alert Details"
+msgstr ""
+
+#: ../../management.rst:336
+# 77c8d073d21f41859f495f2b0120f7ef
+msgid "The supported protocol is SNMP version 2."
+msgstr ""
+
+#: ../../management.rst:338
+# 164535e01fe54071916fc21626d662af
+msgid "Each SNMP trap contains the following information: message, podId, dataCenterId, clusterId, and generationTime."
+msgstr ""
+
+#: ../../management.rst:343
+# be99b465676b4d13ae21a9bd33ff94ef
+msgid "Syslog Alert Details"
+msgstr ""
+
+#: ../../management.rst:345
+# 653fb8fc18ea4f17ab01fe630ed6783b
+msgid "CloudStack generates a syslog message for every alert. Each syslog message incudes the fields alertType, message, podId, dataCenterId, and clusterId, in the following format. If any field does not have a valid value, it will not be included."
+msgstr ""
+
+#: ../../management.rst:354
+# 7c74aa344fe948a39e5bff24928b78fa
+msgid "For example:"
+msgstr ""
+
+#: ../../management.rst:361
+# b3bcf49651e44cc189085099c9309174
+msgid "Configuring SNMP and Syslog Managers"
+msgstr ""
+
+#: ../../management.rst:363
+# b5638ebd1bd5442ab77995897186ed0c
+msgid "To configure one or more SNMP managers or Syslog managers to receive alerts from CloudStack:"
+msgstr ""
+
+#: ../../management.rst:366
+# 377884390b154436a6ce3913008b664c
+msgid "For an SNMP manager, install the CloudStack MIB file on your SNMP manager system. This maps the SNMP OIDs to trap types that can be more easily read by users. The file must be publicly available. For more information on how to install this file, consult the documentation provided with the SNMP manager."
+msgstr ""
+
+#: ../../management.rst:372
+# a32632406531434cbf5c4c261b1f69b6
+msgid "Edit the file /etc/cloudstack/management/log4j-cloud.xml."
+msgstr ""
+
+#: ../../management.rst:378
+# 8ba1745b7c924d888e2595a379d2db32
+msgid "Add an entry using the syntax shown below. Follow the appropriate example depending on whether you are adding an SNMP manager or a Syslog manager. To specify multiple external managers, separate the IP addresses and other configuration values with commas (,)."
+msgstr ""
+
+#: ../../management.rst:384
+# 6cd8468c57974817b400436e8e445394
+msgid "The recommended maximum number of SNMP or Syslog managers is 20 for each."
+msgstr ""
+
+#: ../../management.rst:387
+# d399f22c73ea4836a3776bd53493aaf9
+msgid "The following example shows how to configure two SNMP managers at IP addresses 10.1.1.1 and 10.1.1.2. Substitute your own IP addresses, ports, and communities. Do not change the other values (name, threshold, class, and layout values)."
+msgstr ""
+
+#: ../../management.rst:405
+# 57b464a769fd4128a163f5613f5f1c96
+msgid "The following example shows how to configure two Syslog managers at IP addresses 10.1.1.1 and 10.1.1.2. Substitute your own IP addresses. You can set Facility to any syslog-defined value, such as LOCAL0 - LOCAL7. Do not change the other values."
+msgstr ""
+
+#: ../../management.rst:421
+# 9ac4b5f945144653a9fb6df9185afba4
+msgid "If your cloud has multiple Management Server nodes, repeat these steps to edit log4j-cloud.xml on every instance."
+msgstr ""
+
+#: ../../management.rst:424
+# d82882ad1f8e447fb1ddbf2141ca0f1e
+msgid "If you have made these changes while the Management Server is running, wait a few minutes for the change to take effect."
+msgstr ""
+
+#: ../../management.rst:427
+# c74a110e35d5496db9637e208ca69f0c
+msgid "**Troubleshooting:** If no alerts appear at the configured SNMP or Syslog manager after a reasonable amount of time, it is likely that there is an error in the syntax of the <appender> entry in log4j-cloud.xml. Check to be sure that the format and settings are correct."
+msgstr ""
+
+#: ../../management.rst:435
+# 6e66a0c8054b4278923a1680c1d13f92
+msgid "Deleting an SNMP or Syslog Manager"
+msgstr ""
+
+#: ../../management.rst:437
+# daed36b7b2304574be3a327f0fdaae34
+msgid "To remove an external SNMP manager or Syslog manager so that it no longer receives alerts from CloudStack, remove the corresponding entry from the file ``/etc/cloudstack/management/log4j-cloud.xml``."
+msgstr ""
+
+#: ../../management.rst:443
+# 13024d28ec5a4e0d9d54dc264f048c4c
+msgid "Customizing the Network Domain Name"
+msgstr ""
+
+#: ../../management.rst:445
+# 47fe94d226e941e8971730847123ac7e
+msgid "The root administrator can optionally assign a custom DNS suffix at the level of a network, account, domain, zone, or entire CloudStack installation, and a domain administrator can do so within their own domain. To specify a custom domain name and put it into effect, follow these steps."
+msgstr ""
+
+#: ../../management.rst:451
+# 12a0d889b85a42dfb2f7a37556be8592
+msgid "Set the DNS suffix at the desired scope"
+msgstr ""
+
+#: ../../management.rst:453
+# 8f9f57e29f9c404d9930091f8630a427
+msgid "At the network level, the DNS suffix can be assigned through the UI when creating a new network, as described in `“Adding an Additional Guest Network” <networking2#adding-an-additional-guest-network>`_ or with the updateNetwork command in the CloudStack API."
+msgstr ""
+
+#: ../../management.rst:459
+# c091289d2eee46e89ea79afc752a76bf
+msgid "At the account, domain, or zone level, the DNS suffix can be assigned with the appropriate CloudStack API commands: createAccount, editAccount, createDomain, editDomain, createZone, or editZone."
+msgstr ""
+
+#: ../../management.rst:464
+# 3aa8bfbb66e6499eaf26bd3d496d6bf8
+msgid "At the global level, use the configuration parameter guest.domain.suffix. You can also use the CloudStack API command updateConfiguration. After modifying this global configuration, restart the Management Server to put the new setting into effect."
+msgstr ""
+
+#: ../../management.rst:469
+# ea55aed82e8440d191210e6219afd4b4
+msgid "To make the new DNS suffix take effect for an existing network, call the CloudStack API command updateNetwork. This step is not necessary when the DNS suffix was specified while creating a new network."
+msgstr ""
+
+#: ../../management.rst:473
+# c4c8780f62264aef9166fb7abb03b23d
+msgid "The source of the network domain that is used depends on the following rules."
+msgstr ""
+
+#: ../../management.rst:476
+# ed54e22f6c384a979fdd24525a23d6f4
+msgid "For all networks, if a network domain is specified as part of a network's own configuration, that value is used."
+msgstr ""
+
+#: ../../management.rst:479
+# b62736506f044912b7508f5bcfca6b0b
+msgid "For an account-specific network, the network domain specified for the account is used. If none is specified, the system looks for a value in the domain, zone, and global configuration, in that order."
+msgstr ""
+
+#: ../../management.rst:483
+# e4424d33ec9549389255552629bbdd2a
+msgid "For a domain-specific network, the network domain specified for the domain is used. If none is specified, the system looks for a value in the zone and global configuration, in that order."
+msgstr ""
+
+#: ../../management.rst:487
+# 3d1ebf272ba647ef8f54fcd126b4806c
+msgid "For a zone-specific network, the network domain specified for the zone is used. If none is specified, the system looks for a value in the global configuration."
+msgstr ""
+
+#: ../../management.rst:493
+# b6795b367f9a4a56bd542d1303ef6706
+msgid "Stopping and Restarting the Management Server"
+msgstr ""
+
+#: ../../management.rst:495
+# bbd28a885afc4bd6918951b631b80c85
+msgid "The root administrator will need to stop and restart the Management Server from time to time."
+msgstr ""
+
+#: ../../management.rst:498
+# 0d670244a1804343a1935015f8eaa6fb
+msgid "For example, after changing a global configuration parameter, a restart is required. If you have multiple Management Server nodes, restart all of them to put the new parameter value into effect consistently throughout the cloud.."
+msgstr ""
+
+#: ../../management.rst:503
+# 180fc3fdda44467f97b04959693747c5
+msgid "To stop the Management Server, issue the following command at the operating system prompt on the Management Server node:"
+msgstr ""
+
+#: ../../management.rst:510
+# 02d90290579d496098aed77584f7a2d3
+msgid "To start the Management Server:"
+msgstr ""
+
diff --git a/source/adminguide/locale/pot/networking.pot b/source/adminguide/locale/pot/networking.pot
new file mode 100644
index 0000000..0c5c206
--- /dev/null
+++ b/source/adminguide/locale/pot/networking.pot
@@ -0,0 +1,765 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 
+# This file is distributed under the same license as the Apache CloudStack Administration Documentation package.
+# FIRST AUTHOR <EM...@ADDRESS>, YEAR.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: Apache CloudStack Administration Documentation 4\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2014-06-30 12:52+0200\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EM...@ADDRESS>\n"
+"Language-Team: LANGUAGE <LL...@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#: ../../networking.rst:18
+# e178ac0be7b0492e8a2edc6ed9be7a7b
+msgid "Setting Up Networking for Users"
+msgstr ""
+
+#: ../../networking.rst:21
+# 04f3cd2def1648f2a118dc72cdd5a592
+msgid "Overview of Setting Up Networking for Users"
+msgstr ""
+
+#: ../../networking.rst:23
+# 60188130ecb74037bd537749bcaf4750
+msgid "People using cloud infrastructure have a variety of needs and preferences when it comes to the networking services provided by the cloud. As a CloudStack administrator, you can do the following things to set up networking for your users:"
+msgstr ""
+
+#: ../../networking.rst:28
+# fb8952bb97144229abe5a477941ae76a
+msgid "Set up physical networks in zones"
+msgstr ""
+
+#: ../../networking.rst:30
+# 8dd6941ef2c54c6bbabf956d9eb0680a
+msgid "Set up several different providers for the same service on a single physical network (for example, both Cisco and Juniper firewalls)"
+msgstr ""
+
+#: ../../networking.rst:33
+# d4c8d144d71e47c7b10f71c182941308
+msgid "Bundle different types of network services into network offerings, so users can choose the desired network services for any given virtual machine"
+msgstr ""
+
+#: ../../networking.rst:37
+# f5309ffd41a14f77a9dd77113c106332
+msgid "Add new network offerings as time goes on so end users can upgrade to a better class of service on their network"
+msgstr ""
+
+#: ../../networking.rst:40
+# 13b07adc896a416793148e27ab919b13
+msgid "Provide more ways for a network to be accessed by a user, such as through a project of which the user is a member"
+msgstr ""
+
+#: ../../networking.rst:45
+# 75c4f2f501724f68be26715201e81f13
+msgid "About Virtual Networks"
+msgstr ""
+
+#: ../../networking.rst:47
+# 6e8b5c92233f49618f96673822e130e6
+msgid "A virtual network is a logical construct that enables multi-tenancy on a single physical network. In CloudStack a virtual network can be shared or isolated."
+msgstr ""
+
+#: ../../networking.rst:53
+# e96b2f098a274b148edc9883c7424a27
+msgid "Isolated Networks"
+msgstr ""
+
+#: ../../networking.rst:55
+# 3358619f0382468a9d2f2aea99522408
+msgid "An isolated network can be accessed only by virtual machines of a single account. Isolated networks have the following properties."
+msgstr ""
+
+#: ../../networking.rst:58
+# c84b0ce76be64977bad2361a036a55cf
+msgid "Resources such as VLAN are allocated and garbage collected dynamically"
+msgstr ""
+
+#: ../../networking.rst:61
+# 3eb29ededba94d0dbcb168491b1acda6
+msgid "There is one network offering for the entire network"
+msgstr ""
+
+#: ../../networking.rst:63
+# ff059c44a53e4765b488337444f9fd70
+msgid "The network offering can be upgraded or downgraded but it is for the entire network"
+msgstr ""
+
+#: ../../networking.rst:66
+# d147367777724c05a61626c7756aae05
+msgid "For more information, see `“Configure Guest Traffic in an Advanced Zone” <networking2.html#configure-guest-traffic-in-an-advanced-zone>`_."
+msgstr ""
+
+#: ../../networking.rst:71
+# 9cb58dfba63248058b6e4c2370250e1f
+msgid "Shared Networks"
+msgstr ""
+
+#: ../../networking.rst:73
+# 4b159336d5054af78283deb65966e56d
+msgid "A shared network can be accessed by virtual machines that belong to many different accounts. Network Isolation on shared networks is accomplished by using techniques such as security groups, which is supported only in Basic zones in CloudStack 3.0.3 and later versions."
+msgstr ""
+
+#: ../../networking.rst:78
+# 0eed59cfbc8447e98bc84e58489e3ae7
+msgid "Shared Networks are created by the administrator"
+msgstr ""
+
+#: ../../networking.rst:80
+# b29eadf838f449549e16a2e745f711af
+msgid "Shared Networks can be designated to a certain domain"
+msgstr ""
+
+#: ../../networking.rst:82
+# 956864b9c95e4fb98178b4a0ad4918d3
+msgid "Shared Network resources such as VLAN and physical network that it maps to are designated by the administrator"
+msgstr ""
+
+#: ../../networking.rst:85
+# a9b84145482e4171bdf228084a5d51f4
+msgid "Shared Networks can be isolated by security groups"
+msgstr ""
+
+#: ../../networking.rst:87
+# 345abc742c6749aeb975b3453c70c387
+msgid "Public Network is a shared network that is not shown to the end users"
+msgstr ""
+
+#: ../../networking.rst:89
+# 743e27f0ef1d415180cce8da2bb79724
+msgid "Source NAT per zone is not supported in Shared Network when the service provider is virtual router. However, Source NAT per account is supported. For information, see `“Configuring a Shared Guest Network” <networking2.html#configuring-a-shared-guest-network>`_."
+msgstr ""
+
+#: ../../networking.rst:96
+# dfed0497ec374d71927a32da736f6b28
+msgid "Runtime Allocation of Virtual Network Resources"
+msgstr ""
+
+#: ../../networking.rst:98
+# 33c1cc37caa3449d8a22888ee5706153
+msgid "When you define a new virtual network, all your settings for that network are stored in CloudStack. The actual network resources are activated only when the first virtual machine starts in the network. When all virtual machines have left the virtual network, the network resources are garbage collected so they can be allocated again. This helps to conserve network resources."
+msgstr ""
+
+#: ../../networking.rst:107
+# c7699333b3c747f09b34f3a541caa725
+msgid "Network Service Providers"
+msgstr ""
+
+#: ../../networking.rst:110
+# 90bd799fd2444d978136f72070afd1ca
+msgid "For the most up-to-date list of supported network service providers, see the CloudStack UI or call `listNetworkServiceProviders`."
+msgstr ""
+
+#: ../../networking.rst:113
+# 3f97bb088f7240d99034a78ca6adf65f
+msgid "A service provider (also called a network element) is hardware or virtual appliance that makes a network service possible; for example, a firewall appliance can be installed in the cloud to provide firewall service. On a single network, multiple providers can provide the same network service. For example, a firewall service may be provided by Cisco or Juniper devices in the same physical network."
+msgstr ""
+
+#: ../../networking.rst:120
+# e52ed5139a664c31acccd845de73897d
+msgid "You can have multiple instances of the same service provider in a network (say, more than one Juniper SRX device)."
+msgstr ""
+
+#: ../../networking.rst:123
+# 013a36e42a254aaa98b7e3ad9ea97db8
+msgid "If different providers are set up to provide the same service on the network, the administrator can create network offerings so users can specify which network service provider they prefer (along with the other choices offered in network offerings). Otherwise, CloudStack will choose which provider to use whenever the service is called for."
+msgstr ""
+
+#: ../../networking.rst:129
+# eb5e7f69942b448f906dc822400a348c
+msgid "*Supported Network Service Providers*"
+msgstr ""
+
+#: ../../networking.rst:131
+# d43ecfbdacb84dac9d6ffe5229f277a3
+msgid "CloudStack ships with an internal list of the supported service providers, and you can choose from this list when creating a network offering."
+msgstr ""
+
+#: ../../networking.rst:136
+# 5dd3d24c6aa149cd8be77c9e90e924fa
+msgid "Virtual Router"
+msgstr ""
+
+#: ../../networking.rst:136
+# 8f9be66568214ef19761bdd0b1e87a0a
+msgid "Citrix NetScaler"
+msgstr ""
+
+#: ../../networking.rst:136
+# dccb0ff066124e7ca8f1f4b1df9b566a
+msgid "Juniper SRX"
+msgstr ""
+
+#: ../../networking.rst:136
+# b6c9b2cf119641999eeded8e8069824f
+msgid "F5 BigIP"
+msgstr ""
+
+#: ../../networking.rst:136
+# 4eec0320581e47cea2b8b9a6eb5c5b70
+msgid "Host based (KVM/Xen)"
+msgstr ""
+
+#: ../../networking.rst:139
+# 2c2f1239e908471a929feb91a02e08dd
+msgid "Remote Access VPN"
+msgstr ""
+
+#: ../../networking.rst:139
+#: ../../networking.rst:141
+#: ../../networking.rst:143
+#: ../../networking.rst:143
+#: ../../networking.rst:145
+#: ../../networking.rst:145
+#: ../../networking.rst:145
+#: ../../networking.rst:147
+#: ../../networking.rst:149
+#: ../../networking.rst:151
+#: ../../networking.rst:151
+#: ../../networking.rst:153
+#: ../../networking.rst:153
+#: ../../networking.rst:153
+#: ../../networking.rst:155
+#: ../../networking.rst:155
+# 3ae9d08f24164c359e5553b13dd96db0
+# 0c7c9adabf9449babcb4553e3a59b52b
+# 411fef44341e42758013621c4a23b6b6
+# 6c934e881e7849368f5400433ea69f81
+# 1fc336068db6481183d8a01c5746f5e0
+# 8a397af8cc344e41b52173b2d9bce329
+# 8a7faf6012614a33a03fce7b63e06032
+# f4b01e6ad27f435bbe4aa4b14adc6cd9
+# 60fc90d0645a4e70a2b43c269d7d92ab
+# 72abbb0d60bb43e7ac7ca73f206aa8dd
+# 3f6508ced2f04ac2adcd337ac022d6b0
+# 5492ba67a1304fdb9b75910ef384ac85
+# 1b2c1c6af0814e59bd1d64623dec20d6
+# 76efa1585e2241eaaae3e5a45da37007
+# 933c860bae084ab4846ad9f7270712aa
+# c38c824dc105481f82f564a1071efb74
+msgid "Yes"
+msgstr ""
+
+#: ../../networking.rst:139
+#: ../../networking.rst:139
+#: ../../networking.rst:139
+#: ../../networking.rst:139
+#: ../../networking.rst:141
+#: ../../networking.rst:141
+#: ../../networking.rst:141
+#: ../../networking.rst:141
+#: ../../networking.rst:143
+#: ../../networking.rst:143
+#: ../../networking.rst:143
+#: ../../networking.rst:145
+#: ../../networking.rst:145
+#: ../../networking.rst:147
+#: ../../networking.rst:147
+#: ../../networking.rst:147
+#: ../../networking.rst:147
+#: ../../networking.rst:149
+#: ../../networking.rst:149
+#: ../../networking.rst:149
+#: ../../networking.rst:149
+#: ../../networking.rst:151
+#: ../../networking.rst:151
+#: ../../networking.rst:151
+#: ../../networking.rst:153
+#: ../../networking.rst:153
+#: ../../networking.rst:155
+#: ../../networking.rst:155
+#: ../../networking.rst:155
+# d7b2c2af7ecd47769b0c7bb3013e1bbd
+# beb488a16e4646b3aa87280ad9216415
+# ad48bd439e3148fa94443e2df8acd5a1
+# 5151e216286b45c3b574d6658543a92c
+# ebc177c1de7040e687bb410d7c258141
+# c4efe853b93e471b814a74e0ed31f17d
+# e8ffc6413ca549d69b9a74e6508574d1
+# 8245b2e9c1934761a766679012c0a805
+# 16ec8446477c4c68aabd30136ee67fc0
+# 8a8f9ec35bea40f1853aba71a675887e
+# ec884b7505904c66b59ae39b287f3682
+# a1222a93d01240518b5a74fc57aee793
+# e4317cd2542d43ab90a5f054e18a7e58
+# 82eb13cd8e6a4c14828982cb7c145778
+# fdceedef2f9e43bbbb62a4fb09483cf2
+# 10e8e962affb46bd999d66cae4c189c0
+# 0c5c555a0d3748ac9a84b51b0aaff10a
+# 07903eb7e9fc46fbb91c64c77357409f
+# 98c2b214043b41dea4181a3d1d4726d8
+# ce61ff1d67ff4e90a5a5a722d0fef5f0
+# ded424a7c1b345f398e02e70edea8a5a
+# 9feb3d9ea53b45c5a8e95492710b7124
+# 562866fe2ede4c5f838067549ca5b4bd
+# f21d80c3b07e4fd69b54807235ed3cdb
+# e2d5fa4c2d874e8e90d4022e41f6a3ef
+# 4f7bcdd07de343638f1983951581d2a9
+# 6491fc2c462b4ae5ace77aa2cb534435
+# 248462887faa478ab6a39350b06d8262
+# 5f0d4dc5583a4a2eab7336f826b54b67
+msgid "No"
+msgstr ""
+
+#: ../../networking.rst:141
+# ab9d28c06dcf43d6b43310410d730272
+msgid "DNS/DHCP/User Data"
+msgstr ""
+
+#: ../../networking.rst:143
+#: ../../networking.rst:180
+#: ../../networking.rst:288
+# ec9a836945d54daa80b2790549b0e124
+# 98b80ddeb60c417e839a5e695b989f52
+# 155333ae90b64d45959ef29649a45d44
+msgid "Firewall"
+msgstr ""
+
+#: ../../networking.rst:145
+#: ../../networking.rst:178
+# ec3524d24a7c47479fbc5f696c94c8ba
+# 5d871878b8f6400babacd35334ff571b
+msgid "Load Balancing"
+msgstr ""
+
+#: ../../networking.rst:147
+# e9f00e30da4347368893885b9ebf0951
+msgid "Elastic IP"
+msgstr ""
+
+#: ../../networking.rst:149
+# 2665ea2a6b90470e81ee706892bc8f12
+msgid "Elastic LB"
+msgstr ""
+
+#: ../../networking.rst:151
+#: ../../networking.rst:172
+#: ../../networking.rst:289
+# b07356b446e34c669846ad2c208ed183
+# 522b28c564644bf68213f95712c5b120
+# 2177095ff4a24da29d588bb4cd3c2f4a
+msgid "Source NAT"
+msgstr ""
+
+#: ../../networking.rst:153
+#: ../../networking.rst:174
+#: ../../networking.rst:292
+# eea6bbfe102d498e8fed5cb73cc69b0d
+# c02a1aa3d43f4cde9668b0c049f5ca68
+# fdd23b4cdd3f4aa4a540bf84253e6a5b
+msgid "Static NAT"
+msgstr ""
+
+#: ../../networking.rst:155
+#: ../../networking.rst:176
+#: ../../networking.rst:295
+# b4c037f8d0f1486a8b571d432c94dfc2
+# 218d3d03262e42b2aff11ea6d99f0a49
+# 3ec6fc2e436743f7bf4b9704948e4af3
+msgid "Port Forwarding"
+msgstr ""
+
+#: ../../networking.rst:160
+# 479f4b962b404a428355bb406c787cd9
+msgid "Network Offerings"
+msgstr ""
+
+#: ../../networking.rst:163
+# 25cda5fdd680428d82d9dc0b90b9da3f
+msgid "For the most up-to-date list of supported network services, see the CloudStack UI or call listNetworkServices."
+msgstr ""
+
+#: ../../networking.rst:166
+# 746c329fee3d40298682a774fc0e1ce0
+msgid "A network offering is a named set of network services, such as:"
+msgstr ""
+
+#: ../../networking.rst:168
+#: ../../networking.rst:283
+# 1f84716ebc364d34a628de273bfae124
+# 50ebc53bb5124166b60910b97ac86bc4
+msgid "DHCP"
+msgstr ""
+
+#: ../../networking.rst:170
+#: ../../networking.rst:284
+# 883e0ebe77d94552b3e24415615a7bd9
+# 206e31a90b27475a957f3a6347b7e15d
+msgid "DNS"
+msgstr ""
+
+#: ../../networking.rst:182
+#: ../../networking.rst:298
+# c7ba4a3ce199420a8e1ffa59b6b5aa77
+# e018337607ad4a9d90fe4ef3ab26189e
+msgid "VPN"
+msgstr ""
+
+#: ../../networking.rst:184
+# 0c8566ee7245401e89972f62635febae
+msgid "(Optional) Name one of several available providers to use for a given service, such as Juniper for the firewall"
+msgstr ""
+
+#: ../../networking.rst:187
+# 010067ad73c94e95ad457ead1a816c4e
+msgid "(Optional) Network tag to specify which physical network to use"
+msgstr ""
+
+#: ../../networking.rst:189
+# 27fc0e1384a041e280aad1d5c6497be1
+msgid "When creating a new VM, the user chooses one of the available network offerings, and that determines which network services the VM can use."
+msgstr ""
+
+#: ../../networking.rst:192
+# f0629abea4a3489ab43c6616754295d7
+msgid "The CloudStack administrator can create any number of custom network offerings, in addition to the default network offerings provided by CloudStack. By creating multiple custom network offerings, you can set up your cloud to offer different classes of service on a single multi-tenant physical network. For example, while the underlying physical wiring may be the same for two tenants, tenant A may only need simple firewall protection for their website, while tenant B may be running  [...]
+msgstr ""
+
+#: ../../networking.rst:204
+# f84d6b9ac9d44d159518d14cc74cef39
+msgid "If you create load balancing rules while using a network service offering that includes an external load balancer device such as NetScaler, and later change the network service offering to one that uses the CloudStack virtual router, you must create a firewall rule on the virtual router for each of your existing load balancing rules so that they continue to function."
+msgstr ""
+
+#: ../../networking.rst:211
+# 6a193ad193634184b47093dfab78d48b
+msgid "When creating a new virtual network, the CloudStack administrator chooses which network offering to enable for that network. Each virtual network is associated with one network offering. A virtual network can be upgraded or downgraded by changing its associated network offering. If you do this, be sure to reprogram the physical network to match."
+msgstr ""
+
+#: ../../networking.rst:217
+# 514547d261a44dbba069882e1163a863
+msgid "CloudStack also has internal network offerings for use by CloudStack system VMs. These network offerings are not visible to users but can be modified by administrators."
+msgstr ""
+
+#: ../../networking.rst:223
+# 9eab025e1e0b4102aabc5ed825ad3513
+msgid "Creating a New Network Offering"
+msgstr ""
+
+#: ../../networking.rst:225
+# 101c5c58b3164f2d91d7c068fa2ddc13
+msgid "To create a network offering:"
+msgstr ""
+
+#: ../../networking.rst:227
+# ad144ea208224f0ba8bfd3d268ebaa1a
+msgid "Log in with admin privileges to the CloudStack UI."
+msgstr ""
+
+#: ../../networking.rst:229
+# 7183c1c87f1e4a549609755e3b609e22
+msgid "In the left navigation bar, click Service Offerings."
+msgstr ""
+
+#: ../../networking.rst:231
+# 22b7bae2bee145399e00d289bccc7917
+msgid "In Select Offering, choose Network Offering."
+msgstr ""
+
+#: ../../networking.rst:233
+# ef1169d122904044a6c0246757cbbb46
+msgid "Click Add Network Offering."
+msgstr ""
+
+#: ../../networking.rst:235
+# 3479c8e9a5ef4f458aa9a86725ea9a15
+msgid "In the dialog, make the following choices:"
+msgstr ""
+
+#: ../../networking.rst:237
+# b9faa7d006ed43108fcd33897fea3a5f
+msgid "**Name**. Any desired name for the network offering."
+msgstr ""
+
+#: ../../networking.rst:239
+# 28d48401d7c74f61a6251f06e8e33ea5
+msgid "**Description**. A short description of the offering that can be displayed to users."
+msgstr ""
+
+#: ../../networking.rst:242
+# a81d203163fd41108b4ed24231b5c84d
+msgid "**Network Rate**. Allowed data transfer rate in MB per second."
+msgstr ""
+
+#: ../../networking.rst:244
+# bf34e4c1410c487c81e21d82564c0ceb
+msgid "**Guest Type**. Choose whether the guest network is isolated or shared."
+msgstr ""
+
+#: ../../networking.rst:247
+# 636bbcf4e8ff4e89bc5a3263fa3152fd
+msgid "For a description of this term, see `“About Virtual Networks” <#about-virtual-networks>`_."
+msgstr ""
+
+#: ../../networking.rst:250
+# d9e50bd69812476c975c4eb28509a054
+msgid "**Persistent**. Indicate whether the guest network is persistent or not. The network that you can provision without having to deploy a VM on it is termed persistent network. For more information, see `“Persistent Networks” <networking2.html#persistent-networks>`_."
+msgstr ""
+
+#: ../../networking.rst:256
+# a78fcf61c20941b4a0074b52d456b4fb
+msgid "**Specify VLAN**. (Isolated guest networks only) Indicate whether a VLAN could be specified when this offering is used. If you select this option and later use this network offering while creating a VPC tier or an isolated network, you will be able to specify a VLAN ID for the network you create."
+msgstr ""
+
+#: ../../networking.rst:262
+# 0c356efbc6b1453083e1df0e795cfc3f
+msgid "**VPC**. This option indicate whether the guest network is Virtual Private Cloud-enabled. A Virtual Private Cloud (VPC) is a private, isolated part of CloudStack. A VPC can have its own virtual network topology that resembles a traditional physical network. For more information on VPCs, see `“About Virtual Private Clouds” <networking2.html#about-virtual-private-clouds>`_."
+msgstr ""
+
+#: ../../networking.rst:269
+# 99699a8ca7b8442b9273331bf3721599
+msgid "**Supported Services**. Select one or more of the possible network services. For some services, you must also choose the service provider; for example, if you select Load Balancer, you can choose the CloudStack virtual router or any other load balancers that have been configured in the cloud. Depending on which services you choose, additional fields may appear in the rest of the dialog box."
+msgstr ""
+
+#: ../../networking.rst:277
+# 92f1a16c1ffe4ceb84808c9ba972cbd4
+msgid "Based on the guest network type selected, you can see the following supported services:"
+msgstr ""
+
+#: ../../networking.rst:281
+# 88a57a6470eb454ba571d8fde5632a82
+msgid "Supported Services"
+msgstr ""
+
+#: ../../networking.rst:281
+# d4aa55848ef645639458f908896ac697
+msgid "Description"
+msgstr ""
+
+#: ../../networking.rst:281
+# f8724e6bbae14251ae83b23169d9420f
+msgid "Isolated"
+msgstr ""
+
+#: ../../networking.rst:281
+# 23bd72f8680a493682d6741602166846
+msgid "Shared"
+msgstr ""
+
+#: ../../networking.rst:283
+#: ../../networking.rst:284
+# b488c5b17c004a7b88b330efbc3bc05f
+# 9817c5466dbe4abf99c2de124120bbed
+msgid "For more information, see `“DNS and DHCP” <networking2.html#dns-and-dhcp>`_."
+msgstr ""
+
+#: ../../networking.rst:283
+#: ../../networking.rst:283
+#: ../../networking.rst:284
+#: ../../networking.rst:284
+#: ../../networking.rst:285
+#: ../../networking.rst:285
+#: ../../networking.rst:288
+#: ../../networking.rst:288
+#: ../../networking.rst:289
+#: ../../networking.rst:289
+#: ../../networking.rst:292
+#: ../../networking.rst:292
+#: ../../networking.rst:295
+#: ../../networking.rst:298
+#: ../../networking.rst:300
+#: ../../networking.rst:302
+#: ../../networking.rst:304
+# c4875cd1ba3341f0801c282d362f1d24
+# d065a3aee4944733bff2d01f26b75c7f
+# 9f736e032cce456ebb4f77be38b5e58f
+# 7df1ac5d383948bd84380b75c4e098af
+# 3ba5059895ef4d1c85924407662447ee
+# 3e841c3844b94853b7a8aaaed25cd4ad
+# c77eeef8c5314be099fb3716d3445a66
+# 25f106d12a764b078bb2b6524ad18215
+# f63379e1fe44403bb4b003d91fc04f93
+# 4f4951219e654f71ba852ba5238e8851
+# 15ddd915917341cb80019e9b900a4731
+# 8dacf6aaa0704e9db73a0126c94e16e5
+# 50e87369ed7e48e29d7cb426767a5ed8
+# c1b167740f9e43c2a17a96fbf65930bf
+# 22a23c6ed73740b8a269adc46484bd2a
+# bb47b4ce2443499aa4f5308fec5ed187
+# 8754a866d8d14c92a6556744cf012422
+msgid "Supported"
+msgstr ""
+
+#: ../../networking.rst:285
+# 50819151ad5442aeb2570677b2632a46
+msgid "Load Balancer"
+msgstr ""
+
+#: ../../networking.rst:285
+# b9edc8827ba44d2db0f62206a215e670
+msgid "If you select Load Balancer, you can choose the CloudStack virtual router or any other load balancers that have been configured in the cloud."
+msgstr ""
+
+#: ../../networking.rst:288
+# 2e489054cb1e4a35ac3e90f70c1f1255
+msgid "For more information, see the Administration Guide."
+msgstr ""
+
+#: ../../networking.rst:289
+# 8e117eda9d13423c93e568f0818cc4d9
+msgid "If you select Source NAT, you can choose the CloudStack virtual router or any other Source NAT providers that have been configured in the cloud."
+msgstr ""
+
+#: ../../networking.rst:292
+# aba8109b051a46d89785cb597e382503
+msgid "If you select Static NAT, you can choose the CloudStack virtual router or any other Static NAT providers that have been configured in the cloud."
+msgstr ""
+
+#: ../../networking.rst:295
+# d932fb3f0c49487e8fb03f47c8ec3137
+msgid "If you select Port Forwarding, you can choose the CloudStack virtual router or any other Port Forwarding providers that have been configured in the cloud."
+msgstr ""
+
+#: ../../networking.rst:295
+#: ../../networking.rst:298
+#: ../../networking.rst:300
+#: ../../networking.rst:302
+#: ../../networking.rst:304
+# ba3080b2df494a6194c5a4ec14bd1410
+# 5c07262385d1478c927953b93692e644
+# 23f57ac958b34548a1c2d23a776e1da8
+# c3490a0f19134b8b886f204a4794c427
+# 111a4f3a414c443cb13dcb958326620f
+msgid "Not Supported"
+msgstr ""
+
+#: ../../networking.rst:298
+# ab512b24e90a4f0fbeff2872914232bf
+msgid "For more information, see `“Remote Access VPN” <networking2.html#remote-access-vpn>`_."
+msgstr ""
+
+#: ../../networking.rst:300
+# bc836dbec7dd41098535b7062953abf7
+msgid "User Data"
+msgstr ""
+
+#: ../../networking.rst:300
+# 2ee92986a8924dd1a8704e477e3ce1a6
+msgid "For more information, see `“User Data and Meta Data” <api.html#user-data-and-meta-data>`_."
+msgstr ""
+
+#: ../../networking.rst:302
+# c84e2a3c0cb2440f96442843325bf941
+msgid "Network ACL"
+msgstr ""
+
+#: ../../networking.rst:302
+# 1a00657b608e45b9b31d17dedf1209d9
+msgid "For more information, see `“Configuring Network Access Control List” <networking2.html#configuring-network-access-control-list>`_."
+msgstr ""
+
+#: ../../networking.rst:304
+# 72b47ce7c25a4820af0c52549a594235
+msgid "Security Groups"
+msgstr ""
+
+#: ../../networking.rst:304
+# 08f3a340905b433990695bcc9c4fdd28
+msgid "For more information, see `“Adding a Security Group” <networking2.html#adding-a-security-group>`_."
+msgstr ""
+
+#: ../../networking.rst:309
+# e235b3337dbb400c90ecee3f5837fde2
+msgid "**System Offering**. If the service provider for any of the services selected in Supported Services is a virtual router, the System Offering field appears. Choose the system service offering that you want virtual routers to use in this network. For example, if you selected Load Balancer in Supported Services and selected a virtual router to provide load balancing, the System Offering field appears so you can choose between the CloudStack default system service offering and any cus [...]
+msgstr ""
+
+#: ../../networking.rst:319
+# 34b519afb51c4d1f9b1718b0f32cb527
+msgid "For more information, see `“System Service Offerings” <service_offerings.html#system-service-offerings>`_."
+msgstr ""
+
+#: ../../networking.rst:322
+# 66fb3b1df7164cd6bc37c61a61367d73
+msgid "**LB Isolation**: Specify what type of load balancer isolation you want for the network: Shared or Dedicated."
+msgstr ""
+
+#: ../../networking.rst:325
+# a07b6242746142e18198a5bf7356254f
+msgid "**Dedicated**: If you select dedicated LB isolation, a dedicated load balancer device is assigned for the network from the pool of dedicated load balancer devices provisioned in the zone. If no sufficient dedicated load balancer devices are available in the zone, network creation fails. Dedicated device is a good choice for the high-traffic networks that make full use of the device's resources."
+msgstr ""
+
+#: ../../networking.rst:333
+# 1481728f6860436790f1bbdf1de1b4d0
+msgid "**Shared**: If you select shared LB isolation, a shared load balancer device is assigned for the network from the pool of shared load balancer devices provisioned in the zone. While provisioning CloudStack picks the shared load balancer device that is used by the least number of accounts. Once the device reaches its maximum capacity, the device will not be allocated to a new account."
+msgstr ""
+
+#: ../../networking.rst:341
+# 232eced6797144d7b6cb941627e8d2e6
+msgid "**Mode**: You can select either Inline mode or Side by Side mode:"
+msgstr ""
+
+#: ../../networking.rst:343
+# 7684aca0c54c44fb9871f784de706a13
+msgid "**Inline mode**: Supported only for Juniper SRX firewall and BigF5 load balancer devices. In inline mode, a firewall device is placed in front of a load balancing device. The firewall acts as the gateway for all the incoming traffic, then redirect the load balancing traffic to the load balancer behind it. The load balancer in this case will not have the direct access to the public network."
+msgstr ""
+
+#: ../../networking.rst:351
+# a5a609bdc196450fb249b0fed2b62618
+msgid "**Side by Side**: In side by side mode, a firewall device is deployed in parallel with the load balancer device. So the traffic to the load balancer public IP is not routed through the firewall, and therefore, is exposed to the public network."
+msgstr ""
+
+#: ../../networking.rst:356
+# fddae68fcb5145e68976043eb707eed5
+msgid "**Associate Public IP**: Select this option if you want to assign a public IP address to the VMs deployed in the guest network. This option is available only if"
+msgstr ""
+
+#: ../../networking.rst:360
+# b6cedd774fb4418b8c7f09c30e492ac5
+msgid "Guest network is shared."
+msgstr ""
+
+#: ../../networking.rst:362
+# c011835f1c314df2afcb840630a7ff99
+msgid "StaticNAT is enabled."
+msgstr ""
+
+#: ../../networking.rst:364
+# fcd9521a7c684aaaaacf045798eaaf33
+msgid "Elastic IP is enabled."
+msgstr ""
+
+#: ../../networking.rst:366
+# 9818049dc1484f41b94a2c0c3904838d
+msgid "For information on Elastic IP, see `“About Elastic IP” <networking2.html#about-elastic-ip>`_."
+msgstr ""
+
+#: ../../networking.rst:369
+# 6c9c68a68ab14d30a00460dd3b13f8a6
+msgid "**Redundant router capability**: Available only when Virtual Router is selected as the Source NAT provider. Select this option if you want to use two virtual routers in the network for uninterrupted connection: one operating as the master virtual router and the other as the backup. The master virtual router receives requests from and sends responses to the user’s VM. The backup virtual router is activated only when the master is down. After the failover, the backup becomes the mas [...]
+msgstr ""
+
+#: ../../networking.rst:380
+# e5994ec5233c4a979624fa1fc8593822
+msgid "**Conserve mode**: Indicate whether to use conserve mode. In this mode, network resources are allocated only when the first virtual machine starts in the network. When conservative mode is off, the public IP can only be used for a single service. For example, a public IP used for a port forwarding rule cannot be used for defining other services, such as StaticNAT or load balancing. When the conserve mode is on, you can define more than one service on the same public IP."
+msgstr ""
+
+#: ../../networking.rst:390
+# 6a2faa335b6b42588d747ac83fc4770b
+msgid "If StaticNAT is enabled, irrespective of the status of the conserve mode, no port forwarding or load balancing rule can be created for the IP. However, you can add the firewall rules by using the createFirewallRule command."
+msgstr ""
+
+#: ../../networking.rst:395
+# 029a76d3e8444e15981d3fda29b8982e
+msgid "**Tags**: Network tag to specify which physical network to use."
+msgstr ""
+
+#: ../../networking.rst:397
+# e0d7d2460dba47d29922d3dcf0d16dc5
+msgid "**Default egress policy**: Configure the default policy for firewall egress rules. Options are Allow and Deny. Default is Allow if no egress policy is specified, which indicates that all the egress traffic is accepted when a guest network is created from this offering."
+msgstr ""
+
+#: ../../networking.rst:403
+# 6cf9fba73dda48b8801d8608ce2f52a4
+msgid "To block the egress traffic for a guest network, select Deny. In this case, when you configure an egress rules for an isolated guest network, rules are added to allow the specified traffic."
+msgstr ""
+
+#: ../../networking.rst:407
+# fcfc7b9313f94bbda5ac1afbd8168f7c
+msgid "Click Add."
+msgstr ""
+
diff --git a/source/adminguide/locale/pot/networking/acquiring_an_ip_address.pot b/source/adminguide/locale/pot/networking/acquiring_an_ip_address.pot
new file mode 100644
index 0000000..1d9eb2e
--- /dev/null
+++ b/source/adminguide/locale/pot/networking/acquiring_an_ip_address.pot
@@ -0,0 +1,73 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 
+# This file is distributed under the same license as the Apache CloudStack Administration Documentation package.
+# FIRST AUTHOR <EM...@ADDRESS>, YEAR.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: Apache CloudStack Administration Documentation 4\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2014-06-30 12:52+0200\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EM...@ADDRESS>\n"
+"Language-Team: LANGUAGE <LL...@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#: ../../networking/acquiring_an_ip_address.rst:18
+# aec0c098f53f452cb8665fc7b69cd182
+msgid "Acquiring a New IP Address"
+msgstr ""
+
+#: ../../networking/acquiring_an_ip_address.rst:20
+# 6113064b39bc4682869acf44286131ad
+msgid "Log in to the CloudStack UI as an administrator or end user."
+msgstr ""
+
+#: ../../networking/acquiring_an_ip_address.rst:22
+# ccc7a493b9b940c2b706c15e852b3e93
+msgid "In the left navigation, choose Network."
+msgstr ""
+
+#: ../../networking/acquiring_an_ip_address.rst:24
+# 9a6973f9449e4414a4643a6da352263e
+msgid "Click the name of the network where you want to work with."
+msgstr ""
+
+#: ../../networking/acquiring_an_ip_address.rst:26
+# beaa083fcce64bb48e44a47c9b4ab745
+msgid "Click View IP Addresses."
+msgstr ""
+
+#: ../../networking/acquiring_an_ip_address.rst:28
+# 76867ce630364509a651c09137cab94e
+msgid "Click Acquire New IP."
+msgstr ""
+
+#: ../../networking/acquiring_an_ip_address.rst:30
+# 35698ea68aa24ff79ce9dc09c1d12caf
+msgid "The Acquire New IP window is displayed."
+msgstr ""
+
+#: ../../networking/acquiring_an_ip_address.rst:32
+# 4819ef07622d41fd818aef83d9752ac2
+msgid "Specify whether you want cross-zone IP or not."
+msgstr ""
+
+#: ../../networking/acquiring_an_ip_address.rst:34
+# 342295d34e8e4252b2850d040aca7909
+msgid "If you want Portable IP click Yes in the confirmation dialog. If you want a normal Public IP click No."
+msgstr ""
+
+#: ../../networking/acquiring_an_ip_address.rst:37
+# 9a4837aaa4c940b78c8aa311245b748a
+msgid "For more information on Portable IP, see `\"Portable IPs\" <#portable-ips>`_."
+msgstr ""
+
+#: ../../networking/acquiring_an_ip_address.rst:40
+# 2ee8ad57fe20463893a86f3fe6eb669f
+msgid "Within a few moments, the new IP address should appear with the state Allocated. You can now use the IP address in port forwarding or static NAT rules."
+msgstr ""
+
diff --git a/source/adminguide/locale/pot/networking/advanced_zone_config.pot b/source/adminguide/locale/pot/networking/advanced_zone_config.pot
new file mode 100644
index 0000000..06f6bca
--- /dev/null
+++ b/source/adminguide/locale/pot/networking/advanced_zone_config.pot
@@ -0,0 +1,252 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 
+# This file is distributed under the same license as the Apache CloudStack Administration Documentation package.
+# FIRST AUTHOR <EM...@ADDRESS>, YEAR.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: Apache CloudStack Administration Documentation 4\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2014-06-30 12:52+0200\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EM...@ADDRESS>\n"
+"Language-Team: LANGUAGE <LL...@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#: ../../networking/advanced_zone_config.rst:19
+# bcc6293e20c4470c938be75c5f17196e
+msgid "Advanced Zone Physical Network Configuration"
+msgstr ""
+
+#: ../../networking/advanced_zone_config.rst:21
+# 65ad7a2b34f848cd9f21c2d2d51f06f6
+msgid "Within a zone that uses advanced networking, you need to tell the Management Server how the physical network is set up to carry different kinds of traffic in isolation."
+msgstr ""
+
+#: ../../networking/advanced_zone_config.rst:27
+# 360066243e5b4ffc894a816b7e903923
+msgid "Configure Guest Traffic in an Advanced Zone"
+msgstr ""
+
+#: ../../networking/advanced_zone_config.rst:29
+# ed393c6319d54e98ba44a7577315044b
+msgid "These steps assume you have already logged in to the CloudStack UI. To configure the base guest network:"
+msgstr ""
+
+#: ../../networking/advanced_zone_config.rst:32
+# e3081f9e98e446d6855a2e72cba9849d
+msgid "In the left navigation, choose Infrastructure. On Zones, click View More, then click the zone to which you want to add a network."
+msgstr ""
+
+#: ../../networking/advanced_zone_config.rst:35
+#: ../../networking/advanced_zone_config.rst:87
+# 7e76a728cc8a43778d79ff577c30b3f2
+# 22748233c6cf4d06b5ba94259fe1e6e9
+msgid "Click the Network tab."
+msgstr ""
+
+#: ../../networking/advanced_zone_config.rst:37
+#: ../../networking/advanced_zone_config.rst:89
+# 1c9241340a4d47a58af0ae3e10893ea1
+# 2c90664c2e9647c59a36e2a8f25d1a87
+msgid "Click Add guest network."
+msgstr ""
+
+#: ../../networking/advanced_zone_config.rst:39
+# cbb8ccbe13b34ed88593d4cf688451a1
+msgid "The Add guest network window is displayed:"
+msgstr ""
+
+#: ../../networking/advanced_zone_config.rst:41
+# ef5079e0fa7f4e5c8bac3410c02fa00f
+msgid "|addguestnetwork.png|"
+msgstr ""
+
+#: ../../networking/advanced_zone_config.rst:43
+# ec8bb470f4924bd0af5b256494fbf0f5
+msgid "Provide the following information:"
+msgstr ""
+
+#: ../../networking/advanced_zone_config.rst:45
+# fa32f98dfeb04b68b79b01e6ef0e1fcf
+msgid "**Name**: The name of the network. This will be user-visible"
+msgstr ""
+
+#: ../../networking/advanced_zone_config.rst:47
+# f38e902b2f2c4fe78960c5d37c4a3609
+msgid "**Display Text**: The description of the network. This will be user-visible"
+msgstr ""
+
+#: ../../networking/advanced_zone_config.rst:50
+# c1e74ac05b5a4eacb568d9201d733f74
+msgid "**Zone**: The zone in which you are configuring the guest network."
+msgstr ""
+
+#: ../../networking/advanced_zone_config.rst:52
+# 1bb07d209bd44e82b5f43507bb058db9
+msgid "**Network offering**: If the administrator has configured multiple network offerings, select the one you want to use for this network"
+msgstr ""
+
+#: ../../networking/advanced_zone_config.rst:55
+# a33441c2621f415eb45dbc077a63e7bb
+msgid "**Guest Gateway**: The gateway that the guests should use"
+msgstr ""
+
+#: ../../networking/advanced_zone_config.rst:57
+# 7f50db013a5941939cff931a256abb58
+msgid "**Guest Netmask**: The netmask in use on the subnet the guests will use"
+msgstr ""
+
+#: ../../networking/advanced_zone_config.rst:60
+# 186fd6f7a8de48fea845645978a6b332
+msgid "Click OK."
+msgstr ""
+
+#: ../../networking/advanced_zone_config.rst:64
+# 6c2ac4e12f5f4a8c8788df54295b6e31
+msgid "Configure Public Traffic in an Advanced Zone"
+msgstr ""
+
+#: ../../networking/advanced_zone_config.rst:66
+# 7e91e673073d49e69f1ec92976a0d118
+msgid "In a zone that uses advanced networking, you need to configure at least one range of IP addresses for Internet traffic."
+msgstr ""
+
+#: ../../networking/advanced_zone_config.rst:71
+# c4aa53c641a347da9da814dfc32940a5
+msgid "Configuring a Shared Guest Network"
+msgstr ""
+
+#: ../../networking/advanced_zone_config.rst:73
+# d5ac14718de945a5ae1eda9e0574d9cf
+msgid "Log in to the CloudStack UI as administrator."
+msgstr ""
+
+#: ../../networking/advanced_zone_config.rst:75
+# 9a3fd0f929374352a6cf52cc9790dfb1
+msgid "In the left navigation, choose Infrastructure."
+msgstr ""
+
+#: ../../networking/advanced_zone_config.rst:77
+# dbfd04e800154df197a15cb258be6d3f
+msgid "On Zones, click View More."
+msgstr ""
+
+#: ../../networking/advanced_zone_config.rst:79
+# 7f633e5cc4504dfdaa399fcb8ab6c22e
+msgid "Click the zone to which you want to add a guest network."
+msgstr ""
+
+#: ../../networking/advanced_zone_config.rst:81
+# 173dd051e7a1433d90061cca03962fc4
+msgid "Click the Physical Network tab."
+msgstr ""
+
+#: ../../networking/advanced_zone_config.rst:83
+# e48da344ca7241429e6404ab7b137b39
+msgid "Click the physical network you want to work with."
+msgstr ""
+
+#: ../../networking/advanced_zone_config.rst:85
+# 0e03928f490a4bf5acd9028fed3fd8d8
+msgid "On the Guest node of the diagram, click Configure."
+msgstr ""
+
+#: ../../networking/advanced_zone_config.rst:91
+# 9272a3e9c02b4d3fb7e88cd90f63e56f
+msgid "The Add guest network window is displayed."
+msgstr ""
+
+#: ../../networking/advanced_zone_config.rst:93
+# 271290c4c54643a9a8cc203840b4bb3b
+msgid "Specify the following:"
+msgstr ""
+
+#: ../../networking/advanced_zone_config.rst:95
+# a69cf77fdc48441b9a0e41233bf3d4db
+msgid "**Name**: The name of the network. This will be visible to the user."
+msgstr ""
+
+#: ../../networking/advanced_zone_config.rst:97
+# 924d5df6b0f643c3ad34cdfa02548391
+msgid "**Description**: The short description of the network that can be displayed to users."
+msgstr ""
+
+#: ../../networking/advanced_zone_config.rst:100
+# 8c68c64196cb4b548290e4a3e9851553
+msgid "**VLAN ID**: The unique ID of the VLAN."
+msgstr ""
+
+#: ../../networking/advanced_zone_config.rst:102
+# 0711300a6023445c91c8a4d7926a8e04
+msgid "**Isolated VLAN ID**: The unique ID of the Secondary Isolated VLAN."
+msgstr ""
+
+#: ../../networking/advanced_zone_config.rst:105
+# dbbc4b85106a407f9bb4532a5c1a40a2
+msgid "**Scope**: The available scopes are Domain, Account, Project, and All."
+msgstr ""
+
+#: ../../networking/advanced_zone_config.rst:108
+# 46fd996ba0b241efa0f21c9f22c7c77d
+msgid "**Domain**: Selecting Domain limits the scope of this guest network to the domain you specify. The network will not be available for other domains. If you select Subdomain Access, the guest network is available to all the sub domains within the selected domain."
+msgstr ""
+
+#: ../../networking/advanced_zone_config.rst:114
+# 79bd2bf86f74472db3b4cba26ef143dd
+msgid "**Account**: The account for which the guest network is being created for. You must specify the domain the account belongs to."
+msgstr ""
+
+#: ../../networking/advanced_zone_config.rst:118
+# f3de2d8830134ab195b04b7e4b74b215
+msgid "**Project**: The project for which the guest network is being created for. You must specify the domain the project belongs to."
+msgstr ""
+
+#: ../../networking/advanced_zone_config.rst:122
+# e03c5c4ff8d646cdb1a4029a794765e5
+msgid "**All**: The guest network is available for all the domains, account, projects within the selected zone."
+msgstr ""
+
+#: ../../networking/advanced_zone_config.rst:125
+# 74217dea4b9c4d8faa89e1ea6b2c754e
+msgid "**Network Offering**: If the administrator has configured multiple network offerings, select the one you want to use for this network."
+msgstr ""
+
+#: ../../networking/advanced_zone_config.rst:129
+# 587275eb7b1249e590763c8b0fb81d41
+msgid "**Gateway**: The gateway that the guests should use."
+msgstr ""
+
+#: ../../networking/advanced_zone_config.rst:131
+# 8123de4fbb1d4a1cba01cb099365b448
+msgid "**Netmask**: The netmask in use on the subnet the guests will use."
+msgstr ""
+
+#: ../../networking/advanced_zone_config.rst:133
+# 129d7c2b8ec442cb802ec894eb871959
+msgid "**IP Range**: A range of IP addresses that are accessible from the Internet and are assigned to the guest VMs."
+msgstr ""
+
+#: ../../networking/advanced_zone_config.rst:136
+# 8ea844eb28e94825bdefeba5cc1e143c
+msgid "If one NIC is used, these IPs should be in the same CIDR in the case of IPv6."
+msgstr ""
+
+#: ../../networking/advanced_zone_config.rst:139
+# 1a2dacdd2a984c978ad1455bdb6c04b8
+msgid "**IPv6 CIDR**: The network prefix that defines the guest network subnet. This is the CIDR that describes the IPv6 addresses in use in the guest networks in this zone. To allot IP addresses from within a particular address block, enter a CIDR."
+msgstr ""
+
+#: ../../networking/advanced_zone_config.rst:144
+# d17e32d82ae849139dda243c9ddc9676
+msgid "**Network Domain**: A custom DNS suffix at the level of a network. If you want to assign a special domain name to the guest VM network, specify a DNS suffix."
+msgstr ""
+
+#: ../../networking/advanced_zone_config.rst:148
+# e200da9c829a41109b13173bce7f11ca
+msgid "Click OK to confirm."
+msgstr ""
+
diff --git a/source/adminguide/locale/pot/networking/basic_zone_config.pot b/source/adminguide/locale/pot/networking/basic_zone_config.pot
new file mode 100644
index 0000000..529851f
--- /dev/null
+++ b/source/adminguide/locale/pot/networking/basic_zone_config.pot
@@ -0,0 +1,28 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 
+# This file is distributed under the same license as the Apache CloudStack Administration Documentation package.
+# FIRST AUTHOR <EM...@ADDRESS>, YEAR.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: Apache CloudStack Administration Documentation 4\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2014-06-30 12:52+0200\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EM...@ADDRESS>\n"
+"Language-Team: LANGUAGE <LL...@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#: ../../networking/basic_zone_config.rst:19
+# bf16fca54893437db5aad5aa3f2e6e2c
+msgid "Basic Zone Physical Network Configuration"
+msgstr ""
+
+#: ../../networking/basic_zone_config.rst:21
+# 153ba46cfcf14ac28f2db2730d2e43af
+msgid "In a basic network, configuring the physical network is fairly straightforward. You only need to configure one guest network to carry traffic that is generated by guest VMs. When you first add a zone to CloudStack, you set up the guest network through the Add Zone screens."
+msgstr ""
+
diff --git a/source/adminguide/locale/pot/networking/dns_and_dhcp.pot b/source/adminguide/locale/pot/networking/dns_and_dhcp.pot
new file mode 100644
index 0000000..f43cebc
--- /dev/null
+++ b/source/adminguide/locale/pot/networking/dns_and_dhcp.pot
@@ -0,0 +1,28 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 
+# This file is distributed under the same license as the Apache CloudStack Administration Documentation package.
+# FIRST AUTHOR <EM...@ADDRESS>, YEAR.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: Apache CloudStack Administration Documentation 4\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2014-06-30 12:52+0200\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EM...@ADDRESS>\n"
+"Language-Team: LANGUAGE <LL...@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#: ../../networking/dns_and_dhcp.rst:18
+# 727de7b64d0e4c34bddda54359ed846d
+msgid "DNS and DHCP"
+msgstr ""
+
+#: ../../networking/dns_and_dhcp.rst:20
+# f58ccb2c24bb47c0872a16c74d47f121
+msgid "The Virtual Router provides DNS and DHCP services to the guests. It proxies DNS requests to the DNS server configured on the Availability Zone."
+msgstr ""
+
diff --git a/source/adminguide/locale/pot/networking/elastic_ips.pot b/source/adminguide/locale/pot/networking/elastic_ips.pot
new file mode 100644
index 0000000..0ceb120
--- /dev/null
+++ b/source/adminguide/locale/pot/networking/elastic_ips.pot
@@ -0,0 +1,98 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 
+# This file is distributed under the same license as the Apache CloudStack Administration Documentation package.
+# FIRST AUTHOR <EM...@ADDRESS>, YEAR.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: Apache CloudStack Administration Documentation 4\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2014-06-30 12:52+0200\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EM...@ADDRESS>\n"
+"Language-Team: LANGUAGE <LL...@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#: ../../networking/elastic_ips.rst:18
+# 68f25b7a2e514065b563d7ccdd72f355
+msgid "About Elastic IPs"
+msgstr ""
+
+#: ../../networking/elastic_ips.rst:20
+# bf34049aef4a4cddb2aa0169d49b5281
+msgid "Elastic IP (EIP) addresses are the IP addresses that are associated with an account, and act as static IP addresses. The account owner has the complete control over the Elastic IP addresses that belong to the account. As an account owner, you can allocate an Elastic IP to a VM of your choice from the EIP pool of your account. Later if required you can reassign the IP address to a different VM. This feature is extremely helpful during VM failure. Instead of replacing the VM which i [...]
+msgstr ""
+
+#: ../../networking/elastic_ips.rst:29
+# 8b249afbc2664b01a564524559d5c5fd
+msgid "Similar to the public IP address, Elastic IP addresses are mapped to their associated private IP addresses by using StaticNAT. The EIP service is equipped with StaticNAT (1:1) service in an EIP-enabled basic zone. The default network offering, DefaultSharedNetscalerEIPandELBNetworkOffering, provides your network with EIP and ELB network services if a NetScaler device is deployed in your zone. Consider the following illustration for more details."
+msgstr ""
+
+#: ../../networking/elastic_ips.rst:37
+# deef19d6b1414dbb967743f1b7cef2df
+msgid "|eip-ns-basiczone.png|"
+msgstr ""
+
+#: ../../networking/elastic_ips.rst:39
+# a1f02d4922ed4bbb8941ccc048f0b0b4
+msgid "In the illustration, a NetScaler appliance is the default entry or exit point for the CloudStack instances, and firewall is the default entry or exit point for the rest of the data center. Netscaler provides LB services and staticNAT service to the guest networks. The guest traffic in the pods and the Management Server are on different subnets / VLANs. The policy-based routing in the data center core switch sends the public traffic through the NetScaler, whereas the rest of the da [...]
+msgstr ""
+
+#: ../../networking/elastic_ips.rst:48
+# 28c78bf967714b33884e97cfa4ca307b
+msgid "The EIP work flow is as follows:"
+msgstr ""
+
+#: ../../networking/elastic_ips.rst:50
+# 773cd4ac9b6d4973832aafd2d0cf2f9e
+msgid "When a user VM is deployed, a public IP is automatically acquired from the pool of public IPs configured in the zone. This IP is owned by the VM's account."
+msgstr ""
+
+#: ../../networking/elastic_ips.rst:54
+# 23a70289953d415c81e8dd6ebc86423c
+msgid "Each VM will have its own private IP. When the user VM starts, Static NAT is provisioned on the NetScaler device by using the Inbound Network Address Translation (INAT) and Reverse NAT (RNAT) rules between the public IP and the private IP."
+msgstr ""
+
+#: ../../networking/elastic_ips.rst:60
+# bfa50768ea9b496599aa1804e3437f25
+msgid "Inbound NAT (INAT) is a type of NAT supported by NetScaler, in which the destination IP address is replaced in the packets from the public network, such as the Internet, with the private IP address of a VM in the private network. Reverse NAT (RNAT) is a type of NAT supported by NetScaler, in which the source IP address is replaced in the packets generated by a VM in the private network with the public IP address."
+msgstr ""
+
+#: ../../networking/elastic_ips.rst:67
+# cef50f723bd34b298098fab0ed2c2328
+msgid "This default public IP will be released in two cases:"
+msgstr ""
+
+#: ../../networking/elastic_ips.rst:69
+# 954fad75b2bd41d1b16f50f819a7e300
+msgid "When the VM is stopped. When the VM starts, it again receives a new public IP, not necessarily the same one allocated initially, from the pool of Public IPs."
+msgstr ""
+
+#: ../../networking/elastic_ips.rst:73
+# a5713ccdbc7f41dea9e1fb5bd2a81337
+msgid "The user acquires a public IP (Elastic IP). This public IP is associated with the account, but will not be mapped to any private IP. However, the user can enable Static NAT to associate this IP to the private IP of a VM in the account. The Static NAT rule for the public IP can be disabled at any time. When Static NAT is disabled, a new public IP is allocated from the pool, which is not necessarily be the same one allocated initially."
+msgstr ""
+
+#: ../../networking/elastic_ips.rst:81
+# a8f5524c22bd4ddf82fd8d2d6240b94f
+msgid "For the deployments where public IPs are limited resources, you have the flexibility to choose not to allocate a public IP by default. You can use the Associate Public IP option to turn on or off the automatic public IP assignment in the EIP-enabled Basic zones. If you turn off the automatic public IP assignment while creating a network offering, only a private IP is assigned to a VM when the VM is deployed with that network offering. Later, the user can acquire an IP for the VM a [...]
+msgstr ""
+
+#: ../../networking/elastic_ips.rst:90
+# 89cea0807df84e08bd3c61dbf7579d80
+msgid "For more information on the Associate Public IP option, see `\"Creating a New Network Offering\" <networking.html#creating-a-new-network-offering>`_."
+msgstr ""
+
+#: ../../networking/elastic_ips.rst:94
+# e8e0a7038ebb4ea181ba58c3f4cdc0ed
+msgid "The Associate Public IP feature is designed only for use with user VMs. The System VMs continue to get both public IP and private by default, irrespective of the network offering configuration."
+msgstr ""
+
+#: ../../networking/elastic_ips.rst:98
+# 116e2d3d7abc4e4b89e08770c938b985
+msgid "New deployments which use the default shared network offering with EIP and ELB services to create a shared network in the Basic zone will continue allocating public IPs to each user VM."
+msgstr ""
+
diff --git a/source/adminguide/locale/pot/networking/external_firewalls_and_load_balancers.pot b/source/adminguide/locale/pot/networking/external_firewalls_and_load_balancers.pot
new file mode 100644
index 0000000..ebe9d94
--- /dev/null
+++ b/source/adminguide/locale/pot/networking/external_firewalls_and_load_balancers.pot
@@ -0,0 +1,703 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 
+# This file is distributed under the same license as the Apache CloudStack Administration Documentation package.
+# FIRST AUTHOR <EM...@ADDRESS>, YEAR.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: Apache CloudStack Administration Documentation 4\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2014-06-30 12:52+0200\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EM...@ADDRESS>\n"
+"Language-Team: LANGUAGE <LL...@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:18
+# 9b2c57c96864404ab39ea18532184a3c
+msgid "External Firewalls and Load Balancers"
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:20
+# 406fa3a599d74b6fb0f6a893d839784a
+msgid "CloudStack is capable of replacing its Virtual Router with an external Juniper SRX device and an optional external NetScaler or F5 load balancer for gateway and load balancing services. In this case, the VMs use the SRX as their gateway."
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:27
+# e50bcd9fe60e430d85efc883354624a5
+msgid "About Using a NetScaler Load Balancer"
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:29
+# 1cf32061da5449a2a6dc5887c27b0d72
+msgid "Citrix NetScaler is supported as an external network element for load balancing in zones that use isolated networking in advanced zones. Set up an external load balancer when you want to provide load balancing through means other than CloudStack's provided virtual router."
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:35
+# 188f8456b75c41ffadbc92d637327f54
+msgid "In a Basic zone, load balancing service is supported only if Elastic IP or Elastic LB services are enabled."
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:38
+# 7189603a0b934b4b8f4de77ccc774586
+msgid "When NetScaler load balancer is used to provide EIP or ELB services in a Basic zone, ensure that all guest VM traffic must enter and exit through the NetScaler device. When inbound traffic goes through the NetScaler device, traffic is routed by using the NAT protocol depending on the EIP/ELB configured on the public IP to the private IP. The traffic that is originated from the guest VMs usually goes through the layer 3 router. To ensure that outbound traffic goes through NetScaler [...]
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:52
+# baddaa181f054bb5b0b41e5dcce1387e
+msgid "The NetScaler can be set up in direct (outside the firewall) mode. It must be added before any load balancing rules are deployed on guest VMs in the zone."
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:56
+# 263c8a9eb9d147ad91ae71970d65bd41
+msgid "The functional behavior of the NetScaler with CloudStack is the same as described in the CloudStack documentation for using an F5 external load balancer. The only exception is that the F5 supports routing domains, and NetScaler does not. NetScaler can not yet be used as a firewall."
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:61
+# 79187d2fbfa743c39e8c524304235dc2
+msgid "To install and enable an external load balancer for CloudStack management, see External Guest Load Balancer Integration in the Installation Guide."
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:65
+# d3c851ee525b49599c01646d4d1e2dd5
+msgid "The Citrix NetScaler comes in three varieties. The following summarizes how these variants are treated in CloudStack."
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:68
+# 64aec7c1c44049498dcf6c10b4fa5605
+msgid "**MPX**"
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:70
+# b8df1ce8dfa14d8c8ecc441c6f71748f
+msgid "Physical appliance. Capable of deep packet inspection. Can act as application firewall and load balancer"
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:73
+# 3a1ec0e897e34118a0fbeb78f64a544a
+msgid "In advanced zones, load balancer functionality fully supported without limitation. In basic zones, static NAT, elastic IP (EIP), and elastic load balancing (ELB) are also provided."
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:77
+# 68d5e27c550d40cd921b14324d33692a
+msgid "**VPX**"
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:79
+# 886b66d79fd049739f35d53684946f35
+msgid "Virtual appliance. Can run as VM on XenServer, ESXi, and Hyper-V hypervisors. Same functionality as MPX"
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:82
+# acdf8d15b2b740579349caa99d8ff14f
+msgid "Supported on ESXi and XenServer. Same functional support as for MPX. CloudStack will treat VPX and MPX as the same device type."
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:85
+# 632775a416fd40bfb11895ae39b883e9
+msgid "**SDX**"
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:87
+# 94896445c73d42c7a8a8b30da3d762a9
+msgid "Physical appliance. Can create multiple fully isolated VPX instances on a single appliance to support multi-tenant usage"
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:90
+# 7272ab89523e416fba357a4ceb24b459
+msgid "CloudStack will dynamically provision, configure, and manage the life cycle of VPX instances on the SDX. Provisioned instances are added into CloudStack automatically - no manual configuration by the administrator is required. Once a VPX instance is added into CloudStack, it is treated the same as a VPX on an ESXi host."
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:98
+# e712ff0906b7463083ac7a8f9b19847c
+msgid "Configuring SNMP Community String on a RHEL Server"
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:100
+# a0e11ba7efae4e63a0cd9eb015162722
+msgid "The SNMP Community string is similar to a user id or password that provides access to a network device, such as router. This string is sent along with all SNMP requests. If the community string is correct, the device responds with the requested information. If the community string is incorrect, the device discards the request and does not respond."
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:106
+# d9a8fc53fc4949bda74cb44fbcb04146
+msgid "The NetScaler device uses SNMP to communicate with the VMs. You must install SNMP and configure SNMP Community string for a secure communication between the NetScaler device and the RHEL machine."
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:110
+# 9f7d96642a9b435ab7687ecf88e6f6de
+msgid "Ensure that you installed SNMP on RedHat. If not, run the following command:"
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:117
+# 657a8fba85b14585be4a9165ba95128b
+msgid "Edit the /etc/snmp/snmpd.conf file to allow the SNMP polling from the NetScaler device."
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:120
+# 752d34a607b64dbea0348f5551d5cebc
+msgid "Map the community name into a security name (local and mynetwork, depending on where the request is coming from):"
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:124
+# 07b1fa6ac91c4aa186c434d633b0384e
+msgid "Use a strong password instead of public when you edit the following table."
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:133
+# f8acb0abc31c4fd0ab9300c705ba1f72
+msgid "Setting to 0.0.0.0 allows all IPs to poll the NetScaler server."
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:135
+# 327a4b1c1e4d429c83dc1e1628f8376a
+msgid "Map the security names into group names:"
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:145
+# 193cbe00950147958924521840ba4405
+msgid "Create a view to allow the groups to have the permission to:"
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:151
+# 39191ba80aa24e32898e8a79892fb7cf
+msgid "Grant access with different write permissions to the two groups to the view you created."
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:160
+# ca08ac1ab89442c9a42c7d59efa70e6b
+msgid "Unblock SNMP in iptables."
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:166
+# f161affb624f4139be0750f3dc19f505
+msgid "Start the SNMP service:"
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:172
+# 60eb8801ebf44b97b3b4cc63348013b6
+msgid "Ensure that the SNMP service is started automatically during the system startup:"
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:181
+# 8893688efc574dbfba90b00df9f467bd
+msgid "Initial Setup of External Firewalls and Load Balancers"
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:183
+# 2149019287d549649f77e49102f3a8e2
+msgid "When the first VM is created for a new account, CloudStack programs the external firewall and load balancer to work with the VM. The following objects are created on the firewall:"
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:187
+# 7bec0089c55040c9bcc3b75a4ce9ae0b
+msgid "A new logical interface to connect to the account's private VLAN. The interface IP is always the first IP of the account's private subnet (e.g. 10.1.1.1)."
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:191
+# 5d690ff5c70b4951a41d9ccf663e1e5d
+msgid "A source NAT rule that forwards all outgoing traffic from the account's private VLAN to the public Internet, using the account's public IP address as the source address"
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:195
+# a8b478c2d3334a0aa56507a774978095
+msgid "A firewall filter counter that measures the number of bytes of outgoing traffic for the account"
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:198
+# 438d673ffaa3412c98761796e1c9043c
+msgid "The following objects are created on the load balancer:"
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:200
+# 07491865d4a3476293c53ae24c343c78
+msgid "A new VLAN that matches the account's provisioned Zone VLAN"
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:202
+# 3691e62805b34e95acd2ff232154ca0d
+msgid "A self IP for the VLAN. This is always the second IP of the account's private subnet (e.g. 10.1.1.2)."
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:207
+# 1e387fca9feb4a08825eb2dfe3547fb0
+msgid "Ongoing Configuration of External Firewalls and Load Balancers"
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:209
+# 133336c3018e4957ba148ad3a8f85ed4
+msgid "Additional user actions (e.g. setting a port forward) will cause further programming of the firewall and load balancer. A user may request additional public IP addresses and forward traffic received at these IPs to specific VMs. This is accomplished by enabling static NAT for a public IP address, assigning the IP to a VM, and specifying a set of protocols and port ranges to open. When a static NAT rule is created, CloudStack programs the zone's external firewall with the following [...]
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:218
+# cfcd0d08f25142019221555a1a499683
+msgid "A static NAT rule that maps the public IP address to the private IP address of a VM."
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:221
+# 76e196b931384143a2f1b65467f003dd
+msgid "A security policy that allows traffic within the set of protocols and port ranges that are specified."
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:224
+# b6b755f7fb5a4d4d9495bfe3b0eac10e
+msgid "A firewall filter counter that measures the number of bytes of incoming traffic to the public IP."
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:227
+# 077fa026b5954737b4af75e98a4dd1e8
+msgid "The number of incoming and outgoing bytes through source NAT, static NAT, and load balancing rules is measured and saved on each external element. This data is collected on a regular basis and stored in the CloudStack database."
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:234
+# a882754de1c64a389513a78637f3325d
+msgid "Load Balancer Rules"
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:236
+# 9b95ee51dc6e4026905b950584948d63
+msgid "A CloudStack user or administrator may create load balancing rules that balance traffic received at a public IP to one or more VMs. A user creates a rule, specifies an algorithm, and assigns the rule to a set of VMs."
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:242
+# 7ac5de99c5694e0b89ceb6d4c39e0dfb
+msgid "If you create load balancing rules while using a network service offering that includes an external load balancer device such as NetScaler, and later change the network service offering to one that uses the CloudStack virtual router, you must create a firewall rule on the virtual router for each of your existing load balancing rules so that they continue to function."
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:253
+# b09aa6c58aa84b8f89b3293a64ca17fd
+msgid "Adding a Load Balancer Rule"
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:255
+# 1bc40a00c2f341118db65e97bbbcf986
+msgid "Log in to the CloudStack UI as an administrator or end user."
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:257
+# 57f7d8a61234427abc813c4208e84192
+msgid "In the left navigation, choose Network."
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:259
+# d947318aba7746718816eb5c7e29e9b1
+msgid "Click the name of the network where you want to load balance the traffic."
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:262
+# 20fc7dedf2cf482d94d8977ac64c6b0d
+msgid "Click View IP Addresses."
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:264
+# aff4544b414847af82ceceb0bd4e3b55
+msgid "Click the IP address for which you want to create the rule, then click the Configuration tab."
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:267
+# a84c70dc6b4f4d7c8f5a2d1f82b59355
+msgid "In the Load Balancing node of the diagram, click View All."
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:269
+# 698c929938644fa88bcaa781f68ea4e7
+msgid "In a Basic zone, you can also create a load balancing rule without acquiring or selecting an IP address. CloudStack internally assign an IP when you create the load balancing rule, which is listed in the IP Addresses page when the rule is created."
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:274
+# 2991ed0062324ee88859d10be3c6d280
+msgid "To do that, select the name of the network, then click Add Load Balancer tab. Continue with #7."
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:277
+# f62541afe2764660ba42de5ab1903be0
+msgid "Fill in the following:"
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:279
+# 9d106d6a229045acbfc2622c0c395bd9
+msgid "**Name**: A name for the load balancer rule."
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:281
+# 75090eb93c0c438fbb12cc3c26d20ef9
+msgid "**Public Port**: The port receiving incoming traffic to be balanced."
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:284
+# 61dc53b8703148608a98d96de9b2f3f7
+msgid "**Private Port**: The port that the VMs will use to receive the traffic."
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:287
+# 9e98c799101c44728527da77d95553ee
+msgid "**Algorithm**: Choose the load balancing algorithm you want CloudStack to use. CloudStack supports a variety of well-known algorithms. If you are not familiar with these choices, you will find plenty of information about them on the Internet."
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:292
+# 1fc198ccbf4e4718beba8aaec97b2a38
+msgid "**Stickiness**: (Optional) Click Configure and choose the algorithm for the stickiness policy. See Sticky Session Policies for Load Balancer Rules."
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:296
+# 8d672e758cc24f2da82cbdd82c83ea21
+msgid "**AutoScale**: Click Configure and complete the AutoScale configuration as explained in :ref:`conf-autoscale`."
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:299
+# 33ab79892f344fde975f3d6c32cd9b12
+msgid "**Health Check**: (Optional; NetScaler load balancers only) Click Configure and fill in the characteristics of the health check policy. See :ref:`health-check`."
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:303
+# d643db9463b745c7ac1f19daad8358dd
+msgid "**Ping path (Optional)**: Sequence of destinations to which to send health check queries. Default: / (all)."
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:306
+# b33a72d1050241329dd52806584f0b49
+msgid "**Response time (Optional)**: How long to wait for a response from the health check (2 - 60 seconds). Default: 5 seconds."
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:309
+# 885f1763ea71493ea93ba841259240b3
+msgid "**Interval time (Optional)**: Amount of time between health checks (1 second - 5 minutes). Default value is set in the global configuration parameter lbrule\\_health check\\_time\\_interval."
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:314
+# 82dd529deb534e00b11b709fad1a829f
+msgid "**Healthy threshold (Optional)**: Number of consecutive health check successes that are required before declaring an instance healthy. Default: 2."
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:318
+# 8c946ad8aa9b402ba1d7808681a90216
+msgid "**Unhealthy threshold (Optional)**: Number of consecutive health check failures that are required before declaring an instance unhealthy. Default: 10."
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:322
+# 8bd4120f80ff41368605d05b647ee837
+msgid "Click Add VMs, then select two or more VMs that will divide the load of incoming traffic, and click Apply."
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:325
+# 9720f8ded014448394288000a5c40217
+msgid "The new load balancer rule appears in the list. You can repeat these steps to add more load balancer rules for this IP address."
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:330
+# 3ccedfb3a9324eb1860d1924ac909e3a
+msgid "Sticky Session Policies for Load Balancer Rules"
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:332
+# b33d98749eb5488a8a02cad61861c752
+msgid "Sticky sessions are used in Web-based applications to ensure continued availability of information across the multiple requests in a user's session. For example, if a shopper is filling a cart, you need to remember what has been purchased so far. The concept of \"stickiness\" is also referred to as persistence or maintaining state."
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:338
+# 68678f9c4f934ed796779a0d4121e91a
+msgid "Any load balancer rule defined in CloudStack can have a stickiness policy. The policy consists of a name, stickiness method, and parameters. The parameters are name-value pairs or flags, which are defined by the load balancer vendor. The stickiness method could be load balancer-generated cookie, application-generated cookie, or source-based. In the source-based method, the source IP address is used to identify the user and locate the user's stored data. In the other methods, cooki [...]
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:352
+# bb05b34273814acfb053cac6ffdfe917
+msgid "For the most up to date list of available stickiness methods, see the CloudStack UI or call listNetworks and check the SupportedStickinessMethods capability."
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:360
+# 35aba1c4298e4ecdaaa750f3375b4be2
+msgid "Health Checks for Load Balancer Rules"
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:362
+# d9cc398640dc410ea5c44e614e8d82cd
+msgid "(NetScaler load balancer only; requires NetScaler version 10.0)"
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:364
+# 13a5a45067f34a0b8387527dfaa9d0ce
+msgid "Health checks are used in load-balanced applications to ensure that requests are forwarded only to running, available services. When creating a load balancer rule, you can specify a health check policy. This is in addition to specifying the stickiness policy, algorithm, and other load balancer rule options. You can configure one health check policy per load balancer rule."
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:371
+# 507b3dcc2fbd48a18c5ae46dcb37b341
+msgid "Any load balancer rule defined on a NetScaler load balancer in CloudStack can have a health check policy. The policy consists of a ping path, thresholds to define \"healthy\" and \"unhealthy\" states, health check frequency, and timeout wait interval."
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:376
+# 35f78e270b3e47749e7a677486944ac1
+msgid "When a health check policy is in effect, the load balancer will stop forwarding requests to any resources that are found to be unhealthy. If the resource later becomes available again, the periodic health check will discover it, and the resource will once again be added to the pool of resources that can receive requests from the load balancer. At any given time, the most recent result of the health check is displayed in the UI. For any VM that is attached to a load balancer rule w [...]
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:386
+# bdff04e42c3943e38c182443f757f743
+msgid "You can delete or modify existing health check policies."
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:388
+# eef49f2114c344a58739dcf8f68aac70
+msgid "To configure how often the health check is performed by default, use the global configuration setting healthcheck.update.interval (default value is 600 seconds). You can override this value for an individual health check policy."
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:393
+# 6f13b2ca1fd74ad2a09363a9de9dfa54
+msgid "For details on how to set a health check policy using the UI, see :ref:`adding-lb-rule`."
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:400
+# 6f66a1def18847c0ba2eec5214f58bc4
+msgid "Configuring AutoScale"
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:402
+# 1d10105f71d4436ca70e813d83aa587d
+msgid "AutoScaling allows you to scale your back-end services or application VMs up or down seamlessly and automatically according to the conditions you define. With AutoScaling enabled, you can ensure that the number of VMs you are using seamlessly scale up when demand increases, and automatically decreases when demand subsides. Thus it helps you save compute costs by terminating underused VMs automatically and launching new VMs when you need them, without the need for manual intervention."
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:410
+# f916e1ba803d4d5f93f20a1fc650704f
+msgid "NetScaler AutoScaling is designed to seamlessly launch or terminate VMs based on user-defined conditions. Conditions for triggering a scaleup or scaledown action can vary from a simple use case like monitoring the CPU usage of a server to a complex use case of monitoring a combination of server's responsiveness and its CPU usage. For example, you can configure AutoScaling to launch an additional VM whenever CPU usage exceeds 80 percent for 15 minutes, or to remove a VM whenever CP [...]
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:419
+# fa4167d0761945e6b5552ddc195aa1cb
+msgid "CloudStack uses the NetScaler load balancer to monitor all aspects of a system's health and work in unison with CloudStack to initiate scale-up or scale-down actions."
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:424
+# 25cc6eeee03544bead38d29ffde91c33
+msgid "AutoScale is supported on NetScaler Release 10 Build 74.4006.e and beyond."
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:428
+# f97b092a261142629f674c1cf40ee949
+msgid "Prerequisites"
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:430
+# 0c697f756785488aaa591aa8b9a921cc
+msgid "Before you configure an AutoScale rule, consider the following:"
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:432
+# 8229cf3ea2d24a22bc9707f8f142ca5e
+msgid "Ensure that the necessary template is prepared before configuring AutoScale. When a VM is deployed by using a template and when it comes up, the application should be up and running."
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:437
+# a3b170baceb44749ba1bc8c05a2d5b1c
+msgid "If the application is not running, the NetScaler device considers the VM as ineffective and continues provisioning the VMs unconditionally until the resource limit is exhausted."
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:441
+# df32d04c33ca462ea54e7d716b2d8ffe
+msgid "Deploy the templates you prepared. Ensure that the applications come up on the first boot and is ready to take the traffic. Observe the time requires to deploy the template. Consider this time when you specify the quiet time while configuring AutoScale."
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:446
+# e416b95063a0497fa2b7ca6430c0957c
+msgid "The AutoScale feature supports the SNMP counters that can be used to define conditions for taking scale up or scale down actions. To monitor the SNMP-based counter, ensure that the SNMP agent is installed in the template used for creating the AutoScale VMs, and the SNMP operations work with the configured SNMP community and port by using standard SNMP managers. For example, see `\"Configuring SNMP Community String on a RHELServer\" <#configuring-snmp-community-string-on-a-rhel-ser [...]
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:456
+# 0ac0707e74464bd0840f60e335716a25
+msgid "Ensure that the endpointe.url parameter present in the Global Settings is set to the Management Server API URL. For example, ``http://10.102.102.22:8080/client/api``. In a multi-node Management Server deployment, use the virtual IP address configured in the load balancer for the management server's cluster. Additionally, ensure that the NetScaler device has access to this IP address to provide AutoScale support."
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:464
+# f8d93cd584a54fd8b2a72143d4107323
+msgid "If you update the endpointe.url, disable the AutoScale functionality of the load balancer rules in the system, then enable them back to reflect the changes. For more information see :ref:`update-autoscale`."
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:468
+# f4e671d2a1814ee7936944319291f882
+msgid "If the API Key and Secret Key are regenerated for an AutoScale user, ensure that the AutoScale functionality of the load balancers that the user participates in are disabled and then enabled to reflect the configuration changes in the NetScaler."
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:473
+# 1def24ca3fcf4a9984043a4339307137
+msgid "In an advanced Zone, ensure that at least one VM should be present before configuring a load balancer rule with AutoScale. Having one VM in the network ensures that the network is in implemented state for configuring AutoScale."
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:480
+# d722fd21fbb64e1f8fe5c04b72d39a29
+msgid "Configuration"
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:482
+# aa34165bbbed4360bb6cebfc7b978d91
+msgid "Specify the following:"
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:484
+# 306046475ddb4e789bc88bc1633cdc73
+msgid "|autoscaleateconfig.png|"
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:486
+# 951132877c0f4870b67560ae8035c8eb
+msgid "**Template**: A template consists of a base OS image and application. A template is used to provision the new instance of an application on a scaleup action. When a VM is deployed from a template, the VM can start taking the traffic from the load balancer without any admin intervention. For example, if the VM is deployed for a Web service, it should have the Web server running, the database connected, and so on."
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:494
+# 313bdbb8a05e46239d80664ae76a92cf
+msgid "**Compute offering**: A predefined set of virtual hardware attributes, including CPU speed, number of CPUs, and RAM size, that the user can select when creating a new virtual machine instance. Choose one of the compute offerings to be used while provisioning a VM instance as part of scaleup action."
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:500
+# cd0d1d8ce17d439eb9c360d182e61bc0
+msgid "**Min Instance**: The minimum number of active VM instances that is assigned to a load balancing rule. The active VM instances are the application instances that are up and serving the traffic, and are being load balanced. This parameter ensures that a load balancing rule has at least the configured number of active VM instances are available to serve the traffic."
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:508
+# b883f060ac0a4b669952542845307113
+msgid "If an application, such as SAP, running on a VM instance is down for some reason, the VM is then not counted as part of Min Instance parameter, and the AutoScale feature initiates a scaleup action if the number of active VM instances is below the configured value. Similarly, when an application instance comes up from its earlier down state, this application instance is counted as part of the active instance count and the AutoScale process initiates a scaledown action when the acti [...]
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:518
+# 1062b529c80542fe9f49822dc8e1226b
+msgid "**Max Instance**: Maximum number of active VM instances that **should be assigned to**\\ a load balancing rule. This parameter defines the upper limit of active VM instances that can be assigned to a load balancing rule."
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:523
+# 2f6f81ae0f294d00be1d4501c00d3ef4
+msgid "Specifying a large value for the maximum instance parameter might result in provisioning large number of VM instances, which in turn leads to a single load balancing rule exhausting the VM instances limit specified at the account or domain level."
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:529
+# 80e14b2eba9f4b31bf0f73a8fb4665ac
+msgid "If an application, such as SAP, running on a VM instance is down for some reason, the VM is not counted as part of Max Instance parameter. So there may be scenarios where the number of VMs provisioned for a scaleup action might be more than the configured Max Instance value. Once the application instances in the VMs are up from an earlier down state, the AutoScale feature starts aligning to the configured Max Instance value."
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:537
+# c05f5503e8994d1bbe38126fc1652574
+msgid "Specify the following scale-up and scale-down policies:"
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:539
+# 8b8ee965cf5f45e4a993ef5a61584ee7
+msgid "**Duration**: The duration, in seconds, for which the conditions you specify must be true to trigger a scaleup action. The conditions defined should hold true for the entire duration you specify for an AutoScale action to be invoked."
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:544
+# aef0e1b396cc4f4aa88ea919926bc457
+msgid "**Counter**: The performance counters expose the state of the monitored instances. By default, CloudStack offers four performance counters: Three SNMP counters and one NetScaler counter. The SNMP counters are Linux User CPU, Linux System CPU, and Linux CPU Idle. The NetScaler counter is ResponseTime. The root administrator can add additional counters into CloudStack by using the CloudStack API."
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:551
+# e13329c9be684765967ad40f1ed75b4e
+msgid "**Operator**: The following five relational operators are supported in AutoScale feature: Greater than, Less than, Less than or equal to, Greater than or equal to, and Equal to."
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:555
+# 736606eaa3ac4622b52ed0ab0545ba37
+msgid "**Threshold**: Threshold value to be used for the counter. Once the counter defined above breaches the threshold value, the AutoScale feature initiates a scaleup or scaledown action."
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:559
+# e74122a065ed4373a7c1291eb1291e64
+msgid "**Add**: Click Add to add the condition."
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:561
+# 7d05f0a9ea384a5790999dfcd7fd3647
+msgid "Additionally, if you want to configure the advanced settings, click Show advanced settings, and specify the following:"
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:564
+# 9e8ccf2af53541eea6450c116ba10b0a
+msgid "**Polling interval**: Frequency in which the conditions, combination of counter, operator and threshold, are to be evaluated before taking a scale up or down action. The default polling interval is 30 seconds."
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:569
+# 9a0a8077043d427ba02f39207e648c16
+msgid "**Quiet Time**: This is the cool down period after an AutoScale action is initiated. The time includes the time taken to complete provisioning a VM instance from its template and the time taken by an application to be ready to serve traffic. This quiet time allows the fleet to come up to a stable state before any action can take place. The default is 300 seconds."
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:576
+# d562af8950534ba78cfad860812c91af
+msgid "**Destroy VM Grace Period**: The duration in seconds, after a scaledown action is initiated, to wait before the VM is destroyed as part of scaledown action. This is to ensure graceful close of any pending sessions or transactions being served by the VM marked for destroy. The default is 120 seconds."
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:582
+# b74500ed7cdc4d5e984c9d01a17d6cae
+msgid "**Security Groups**: Security groups provide a way to isolate traffic to the VM instances. A security group is a group of VMs that filter their incoming and outgoing traffic according to a set of rules, called ingress and egress rules. These rules filter network traffic according to the IP address that is attempting to communicate with the VM."
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:589
+# 6e921b5c683943bf8e306cb4cd731b76
+msgid "**Disk Offerings**: A predefined set of disk size for primary data storage."
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:592
+# 8eeeb8c4bf1749e6b405081fce9318ca
+msgid "**SNMP Community**: The SNMP community string to be used by the NetScaler device to query the configured counter value from the provisioned VM instances. Default is public."
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:596
+# 63d93ca18c5245e3aa630d743d5b1fff
+msgid "**SNMP Port**: The port number on which the SNMP agent that run on the provisioned VMs is listening. Default port is 161."
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:599
+# 8e4ead8319ea470ba2e3a6183acf7ce2
+msgid "**User**: This is the user that the NetScaler device use to invoke scaleup and scaledown API calls to the cloud. If no option is specified, the user who configures AutoScaling is applied. Specify another user name to override."
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:604
+# c5ab8b8578de4f5b8e2aa37c414525aa
+msgid "**Apply**: Click Apply to create the AutoScale configuration."
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:608
+# 3d6ec42e045a4082a8798bec5791982a
+msgid "Disabling and Enabling an AutoScale Configuration"
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:610
+# ec5c758cc62a40e587a4b6c4fddb434f
+msgid "If you want to perform any maintenance operation on the AutoScale VM instances, disable the AutoScale configuration. When the AutoScale configuration is disabled, no scaleup or scaledown action is performed. You can use this downtime for the maintenance activities. To disable the AutoScale configuration, click the Disable AutoScale |EnableDisable.png| button."
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:616
+# 0a60f936b205455c98dceed77b11df3c
+msgid "The button toggles between enable and disable, depending on whether AutoScale is currently enabled or not. After the maintenance operations are done, you can enable the AutoScale configuration back. To enable, open the AutoScale configuration page again, then click the Enable AutoScale |EnableDisable.png| button."
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:626
+# f4bb71e85bd344b89fdcb3239a0f51f8
+msgid "Updating an AutoScale Configuration"
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:628
+# 3bf60f14a73d43869794736b33b5aa5b
+msgid "You can update the various parameters and add or delete the conditions in a scaleup or scaledown rule. Before you update an AutoScale configuration, ensure that you disable the AutoScale load balancer rule by clicking the Disable AutoScale button."
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:633
+# f9665a6811b3410ba434ca755c6451f6
+msgid "After you modify the required AutoScale parameters, click Apply. To apply the new AutoScale policies, open the AutoScale configuration page again, then click the Enable AutoScale button."
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:639
+# debb34a5766f45ca8759a81e6401dc05
+msgid "Runtime Considerations"
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:641
+# 57af5a07b00746d1b071d2eb6e80fea1
+msgid "An administrator should not assign a VM to a load balancing rule which is configured for AutoScale."
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:644
+# 7df6035fc7ca442bbbb5d7bd0ea0428b
+msgid "Before a VM provisioning is completed if NetScaler is shutdown or restarted, the provisioned VM cannot be a part of the load balancing rule though the intent was to assign it to a load balancing rule. To workaround, rename the AutoScale provisioned VMs based on the rule name or ID so at any point of time the VMs can be reconciled to its load balancing rule."
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:651
+# 0eca9ec603bb4fc28eaabd868afa3e27
+msgid "Making API calls outside the context of AutoScale, such as destroyVM, on an autoscaled VM leaves the load balancing configuration in an inconsistent state. Though VM is destroyed from the load balancer rule, NetScaler continues to show the VM as a service assigned to a rule."
+msgstr ""
+
diff --git a/source/adminguide/locale/pot/networking/global_server_load_balancing.pot b/source/adminguide/locale/pot/networking/global_server_load_balancing.pot
new file mode 100644
index 0000000..e9acc45
--- /dev/null
+++ b/source/adminguide/locale/pot/networking/global_server_load_balancing.pot
@@ -0,0 +1,573 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 
+# This file is distributed under the same license as the Apache CloudStack Administration Documentation package.
+# FIRST AUTHOR <EM...@ADDRESS>, YEAR.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: Apache CloudStack Administration Documentation 4\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2014-06-30 12:52+0200\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EM...@ADDRESS>\n"
+"Language-Team: LANGUAGE <LL...@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#: ../../networking/global_server_load_balancing.rst:18
+# dcd5b9f2eedc4d1682f64e174cd2cef7
+msgid "Global Server Load Balancing Support"
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:20
+# 6cf6d74b4dde4e5fb05f41ae52822a4a
+msgid "CloudStack supports Global Server Load Balancing (GSLB) functionalities to provide business continuity, and enable seamless resource movement within a CloudStack environment. CloudStack 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 CloudStack."
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:28
+# 7396fe0f91a94dcf8d73474623b3c975
+msgid "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 CloudStack. GSLB functionality works in an Active-Active data center environment."
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:37
+# c1b8feb53b76438681b08acf77c25440
+msgid "About Global Server Load Balancing"
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:39
+# e03a6a1a69b640308c22260d5737533b
+msgid "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 ac [...]
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:51
+# ba32175058a043b081e7045d04a34334
+msgid "Components of GSLB"
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:53
+# 8282609b9ff24cd980a31ea858744fba
+msgid "A typical GSLB environment is comprised of the following components:"
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:55
+# 0c4b0b08a37346789443744bef960c26
+msgid "**GSLB Site**: In CloudStack 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."
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:63
+# e6f8317f00944a5faf27bf059374e211
+msgid "**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."
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:72
+# 0d6074d67e874afaafcced32aa2dcad8
+msgid "**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 CloudStack 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  [...]
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:81
+# 25269a15ffaf4c48880b969ed8e8ff0b
+msgid "**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 ba [...]
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:91
+# a4ae12735c574a18995202afba84a585
+msgid "**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."
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:96
+# 18dae232ea054aad8beb56723f2e9d6d
+msgid "**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 [...]
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:107
+# 9efb5a6ae20d45eab31e7fe7ffc87eab
+msgid "How Does GSLB Works in CloudStack?"
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:109
+# daac6a57d97c4caebd3fa5d2f5f27324
+msgid "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 CloudStack: 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 CloudStack. Tenant-A of the cloud launches a highly available solution by using x [...]
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:126
+# ab85065c7a794a62bb64bb4d17ff62c9
+msgid "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, CloudStack 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 in [...]
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:144
+# 16e02bcf2da14fd48ec4af740ccfc445
+msgid "|gslb.png|"
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:146
+# 7f93cb0f9f2e4bc58cfc7f308c019bda
+msgid "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. CloudStack orchestrates setting up GSLB virtual server 1 on the GSLB service provider at Zone-1. CloudStack 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 st [...]
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:175
+# dcd79b8e29a442d098cb8090a4527144
+msgid "Configuring GSLB"
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:177
+# af3fb04e787447d9976ebb989e847e3d
+msgid "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 s [...]
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:189
+# f12e3e8dd3114cc6ab5febf7d770620a
+msgid "Perform the following as a cloud administrator. As per the example given above, the administrator of xyztelco is the one who sets up GSLB:"
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:192
+# 9579cd3756414bb59e03052c3c4807de
+msgid "In the cloud.dns.name global parameter, specify the DNS name of your tenant's cloud that make use of the GSLB service."
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:195
+# e675df400e4c40079a4b8ac2c3a3a007
+msgid "On the NetScaler side, configure GSLB as given in `Configuring Global Server Load Balancing (GSLB) <http://support.citrix.com/proddocs/topic/netscaler-traffic-management-10-map/ns-gslb-config-con.html>`_:"
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:199
+# 8366d0a33b5d4328b32668eee7db43a7
+msgid "Configuring a standard load balancing setup."
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:201
+# 652a6e0d3f25435bad8a3a37ff14f6de
+msgid "Configure Authoritative DNS, as explained in `Configuring an Authoritative DNS Service <http://support.citrix.com/proddocs/topic/netscaler-traffic-management-10-map/ns-gslb-config-adns-svc-tsk.html>`_."
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:205
+# eb1be7170a664c05818eea4cebcd652c
+msgid "Configure a GSLB site with site name formed from the domain name details."
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:208
+# af0e9c7b27f545b9a2532edf6109ddf3
+msgid "Configure a GSLB site with the site name formed from the domain name."
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:211
+# 6c3c9b0f00314c219b51b9ea4a817b37
+msgid "As per the example given above, the site names are A.xyztelco.com and B.xyztelco.com."
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:214
+# 8bc45e9126194d24824f0e0e2d92ca1b
+msgid "For more information, see `Configuring a Basic GSLB Site <http://support.citrix.com/proddocs/topic/netscaler-traffic-management-10-map/ns-gslb-config-basic-site-tsk.html>`_."
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:217
+# 7276993a8c1f4f089886c5bfce5f4f6e
+msgid "Configure a GSLB virtual server."
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:219
+# 8d0c82c139184d3992209af4d2e54a6c
+msgid "For more information, see `Configuring a GSLB Virtual Server <http://support.citrix.com/proddocs/topic/netscaler-traffic-management-10-map/ns-gslb-config-vsvr-tsk.html>`_."
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:222
+# 7db75bd72fa44709ab7adb82ba26f318
+msgid "Configure a GSLB service for each virtual server."
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:224
+# 7dd4d9aa1c394ed6859a00b0331f3e5b
+msgid "For more information, see `Configuring a GSLB Service <http://support.citrix.com/proddocs/topic/netscaler-traffic-management-10-map/ns-gslb-config-svc-tsk.html>`_."
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:227
+# 30745365545f4cbca1a5ff6fa73a495f
+msgid "Bind the GSLB services to the GSLB virtual server."
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:229
+# f5c32c764b0c44cc9b430cd2c74f5a0b
+msgid "For more information, see `Binding GSLB Services to a GSLB Virtual Server <http://support.citrix.com/proddocs/topic/netscaler-traffic-management-10-map/ns-gslb-bind-svc-vsvr-tsk.html>`_."
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:232
+# 74f55b2693404f1d8b46b1960f0987db
+msgid "Bind domain name to GSLB virtual server. Domain name is obtained from the domain details."
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:235
+# 012a1ab7ff7b422995e21b6709b4c6b3
+msgid "For more information, see `Binding a Domain to a GSLB Virtual Server <http://support.citrix.com/proddocs/topic/netscaler-traffic-management-10-map/ns-gslb-bind-dom-vsvr-tsk.html>`_."
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:238
+# efe8d44a7dc84347bdc932507e0cf417
+msgid "In each zone that are participating in GSLB, add GSLB-enabled NetScaler device."
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:241
+# b4176a11b248487686fbfb80d484f72d
+msgid "For more information, see :ref:`enabling-gslb-in-ns`."
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:243
+# 8fc3da50593741b9863599aee89587e8
+msgid "As a domain administrator/ user perform the following:"
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:245
+# 8c1293eb2d3746e8abb219c5c4cb7290
+msgid "Add a GSLB rule on both the sites."
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:247
+# a78f47a38a364e859b24e482f8eab174
+msgid "See \":ref:`adding-gslb-rule`\"."
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:249
+# 17e3b59ea95e4eb39b1290cea67e4801
+msgid "Assign load balancer rules."
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:251
+# d37f5840c4d34fa9aa990a0bb0610af9
+msgid "See \":ref:`assigning-lb-rule-gslb`\"."
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:255
+# 2553447c986746b582a9f8b495396c3b
+msgid "Prerequisites and Guidelines"
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:257
+# 8627b5c519f04c4bb75b82af96f25418
+msgid "The GSLB functionality is supported both Basic and Advanced zones."
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:259
+# c2b5f208b13f4b07b6755c0a53fa1104
+msgid "GSLB is added as a new network service."
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:261
+# 3c6e0da5ecd148d599a35191c7e92678
+msgid "GSLB service provider can be added to a physical network in a zone."
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:263
+# 6c159f1bc2224bb2b35dd03ec51bc6b1
+msgid "The admin is allowed to enable or disable GSLB functionality at region level."
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:266
+# 6367e49f50d0418c92b7b6fc7cc91a39
+msgid "The admin is allowed to configure a zone as GSLB capable or enabled."
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:268
+# a66b5c6d51534ab492d244d518221776
+msgid "A zone shall be considered as GSLB capable only if a GSLB service provider is provisioned in the zone."
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:271
+# 0ea762e8718b465eaacf40a6118c8f7f
+msgid "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."
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:275
+# ed2130b4027e41e3833699a89ff82708
+msgid "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."
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:278
+# 1b374fea614b459eb39cfbe4f20478c9
+msgid "The users can load balance traffic across the availability zones in the same region or different regions."
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:281
+# 62da6f878356420f9becc6fffbe1ae6d
+msgid "The admin can configure DNS name for the entire cloud."
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:283
+# 799fe9490296493e9d86d0ea8cdc9297
+msgid "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."
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:287
+# 1d6c20de63954971a720227985a74433
+msgid "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."
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:294
+# a7817e36fe2c4ea58737d1a5ae3db30b
+msgid "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."
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:297
+# 971bcd7f3cf24bbbb424a020cc7c06a4
+msgid "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."
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:301
+# 6f3d31dca71d4b608fa90d1eb73ecee2
+msgid "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."
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:305
+# bfaf6196eae343259864ac2443ff5746
+msgid "Statistics is collected from each GSLB virtual server."
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:311
+# d2f3468cd4ac44d58c53e731e50e35dd
+msgid "Enabling GSLB in NetScaler"
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:313
+# d51d618416764b5c843fc13bfd2dfa6d
+msgid "In each zone, add GSLB-enabled NetScaler device for load balancing."
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:315
+# 91d1d3b496c34b179f0b865500b6bf93
+msgid "Log in as administrator to the CloudStack UI."
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:317
+# cc1ae38bffd84c058812510e8495b73f
+msgid "In the left navigation bar, click Infrastructure."
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:319
+# 46ba7c7f81d04aa78f0c04d3d045bc8a
+msgid "In Zones, click View More."
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:321
+# 1feb8d2e09014d9989264c48ece8fc81
+msgid "Choose the zone you want to work with."
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:323
+# 82a50383b1124be48db8d0c5721e9f13
+msgid "Click the Physical Network tab, then click the name of the physical network."
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:326
+# 75224089389e4bee8e89a1caf1dc5880
+msgid "In the Network Service Providers node of the diagram, click Configure."
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:329
+# 410a9b626bf9412a9f482c2df1aac784
+msgid "You might have to scroll down to see this."
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:331
+# 1d32a851fb92436c8e045ccc828641f4
+msgid "Click NetScaler."
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:333
+# af72e8614fc44c60af3004624dba03b1
+msgid "Click Add NetScaler device and provide the following:"
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:335
+# 6290f4f42d054ac28661b16c5366b62f
+msgid "For NetScaler:"
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:337
+# 8e09b55d68a849d089029f2c893e3e97
+msgid "**IP Address**: The IP address of the SDX."
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:339
+# 9b9b4165d2ee4e64b3b0b04390702686
+msgid "**Username/Password**: The authentication credentials to access the device. CloudStack uses these credentials to access the device."
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:343
+# 212ab71ac16a49309da99e2870717faa
+msgid "**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 CloudStack Administration Guide."
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:348
+# 3d72c6cb5cbb49418002a5e3acf1617c
+msgid "**Public interface**: Interface of device that is configured to be part of the public network."
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:351
+# 5bbed919dc2c45008af4312d028cfbd7
+msgid "**Private interface**: Interface of device that is configured to be part of the private network."
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:354
+# fb82ba2e06e34aaf9ab8e8fa8362b43d
+msgid "**GSLB service**: Select this option."
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:356
+# 8a1e3ad262934da086878740aefca5fc
+msgid "**GSLB service Public IP**: The public IP address of the NAT translator for a GSLB service that is on a private network."
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:359
+# 5ca3fc19dd8e4706872b9e3af0652c2f
+msgid "**GSLB service Private IP**: The private IP of the GSLB service."
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:361
+# 8f1a8fd9ec814e02970f7edf85c8fad1
+msgid "**Number of Retries**. Number of times to attempt a command on the device before considering the operation failed. Default is 2."
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:364
+# 2416b7a9e5fa43fdb27834cb7e46253b
+msgid "**Capacity**: The number of networks the device can handle."
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:366
+# c9166740fb2747a7abd4ae6c0851aabc
+msgid "**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."
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:371
+# e7f874eb36ba4cd380f7a50d5bff8909
+msgid "Click OK."
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:377
+# d1556618bd5d4d18862c048d52694dd4
+msgid "Adding a GSLB Rule"
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:379
+#: ../../networking/global_server_load_balancing.rst:423
+# c06bbbd0cb824ecc8ef3d7956571f739
+# 2b618c03ffb14afb99d7e63813820288
+msgid "Log in to the CloudStack UI as a domain administrator or user."
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:381
+#: ../../networking/global_server_load_balancing.rst:425
+# 3b04d23a46774662bbca98318323a71e
+# 62eb7d6a5d9b4256bde0fcafb9f42b7f
+msgid "In the left navigation pane, click Region."
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:383
+#: ../../networking/global_server_load_balancing.rst:427
+# 940f5610d0484910bf9e9ba31728be30
+# 581952b854514ed78884cc712ee4ec94
+msgid "Select the region for which you want to create a GSLB rule."
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:385
+#: ../../networking/global_server_load_balancing.rst:429
+# fc1d362cc95a4668b2a24c7c0f488348
+# 8519e9d4ad6d46989865460e20b186b6
+msgid "In the Details tab, click View GSLB."
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:387
+# f59a742f9f1b4f37b6f0bc0b062028d6
+msgid "Click Add GSLB."
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:389
+# ca546577015a45af8ddcdc3d2ad22f3a
+msgid "The Add GSLB page is displayed as follows:"
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:391
+# b0b6437c269342ff9099b6da9a6d5b9f
+msgid "|gslb-add.png|"
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:393
+# 767ce39d9a094fda85465381d3a93bad
+msgid "Specify the following:"
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:395
+# affa9e59440b4f4e9e6428e887d12582
+msgid "**Name**: Name for the GSLB rule."
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:397
+# 82b72cbf0f8949fdab2de931138620c5
+msgid "**Description**: (Optional) A short description of the GSLB rule that can be displayed to users."
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:400
+# 8a6b82bfcd3a469c838315b17f4cd014
+msgid "**GSLB Domain Name**: A preferred domain name for the service."
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:402
+# ff5539d5f09f48bc80c0cf9dc83dcca0
+msgid "**Algorithm**: (Optional) The algorithm to use to load balance the traffic across the zones. The options are Round Robin, Least Connection, and Proximity."
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:406
+# b07f4dffc105427389bb8e089a71f9f0
+msgid "**Service Type**: The transport protocol to use for GSLB. The options are TCP and UDP."
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:409
+# 03ffe3890f5c4ea79836cfa0cc96986f
+msgid "**Domain**: (Optional) The domain for which you want to create the GSLB rule."
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:412
+# 5d0367f6567241968e5d6cac6f8ab34b
+msgid "**Account**: (Optional) The account on which you want to apply the GSLB rule."
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:415
+#: ../../networking/global_server_load_balancing.rst:439
+# 0161504934d746e39b05e6b50e264faf
+# 8c377e12f8494a009d5eed7e06824fe3
+msgid "Click OK to confirm."
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:421
+# f61c6b78ef4940129243771e21d78f4c
+msgid "Assigning Load Balancing Rules to GSLB"
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:431
+# 54cc7b916ceb420584020f5ff230b79c
+msgid "Select the desired GSLB."
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:433
+# 5e2a1bf3adfc41bab4bea1a489f9bda1
+msgid "Click view assigned load balancing."
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:435
+# 269db9ca8770495f9c5bc08491e61bc6
+msgid "Click assign more load balancing."
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:437
+# eceeb5fccdfa4cac904ef8fb945242c9
+msgid "Select the load balancing rule you have created for the zone."
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:443
+# d8792daad4a94b4589452d5b61f75cd9
+msgid "Known Limitation"
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:445
+# 7424fdf000e3479c910e72fbbaaa0169
+msgid "Currently, CloudStack does not support orchestration of services across the zones. The notion of services and service providers in region are to be introduced."
+msgstr ""
+
diff --git a/source/adminguide/locale/pot/networking/guest_ip_ranges.pot b/source/adminguide/locale/pot/networking/guest_ip_ranges.pot
new file mode 100644
index 0000000..2e32f45
--- /dev/null
+++ b/source/adminguide/locale/pot/networking/guest_ip_ranges.pot
@@ -0,0 +1,33 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 
+# This file is distributed under the same license as the Apache CloudStack Administration Documentation package.
+# FIRST AUTHOR <EM...@ADDRESS>, YEAR.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: Apache CloudStack Administration Documentation 4\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2014-06-30 12:52+0200\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EM...@ADDRESS>\n"
+"Language-Team: LANGUAGE <LL...@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#: ../../networking/guest_ip_ranges.rst:18
+# c4f6e8eb1ed7428a8132309d84e4b1bf
+msgid "Guest IP Ranges"
+msgstr ""
+
+#: ../../networking/guest_ip_ranges.rst:20
+# ef6d3891253c4ed58a8a51c2f86b51dc
+msgid "The IP ranges for guest network traffic are set on a per-account basis by the user. This allows the users to configure their network in a fashion that will enable VPN linking between their guest network and their clients."
+msgstr ""
+
+#: ../../networking/guest_ip_ranges.rst:25
+# 943864c06f494d7ca4f4310246ba996a
+msgid "In shared networks in Basic zone and Security Group-enabled Advanced networks, you will have the flexibility to add multiple guest IP ranges from different subnets. You can add or remove one IP range at a time. For more information, see `\"About Multiple IP Ranges\" <#about-multiple-ip-ranges>`_."
+msgstr ""
+
diff --git a/source/adminguide/locale/pot/networking/guest_traffic.pot b/source/adminguide/locale/pot/networking/guest_traffic.pot
new file mode 100644
index 0000000..4cb5bbb
--- /dev/null
+++ b/source/adminguide/locale/pot/networking/guest_traffic.pot
@@ -0,0 +1,53 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 
+# This file is distributed under the same license as the Apache CloudStack Administration Documentation package.
+# FIRST AUTHOR <EM...@ADDRESS>, YEAR.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: Apache CloudStack Administration Documentation 4\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2014-06-30 12:52+0200\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EM...@ADDRESS>\n"
+"Language-Team: LANGUAGE <LL...@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#: ../../networking/guest_traffic.rst:18
+# 6a1d02b308ae4f228e4104aa95e39ee3
+msgid "Guest Traffic"
+msgstr ""
+
+#: ../../networking/guest_traffic.rst:20
+# 77e0128afe644aa9a04259e24cb22595
+msgid "A network can carry guest traffic only between VMs within one zone. Virtual machines in different zones cannot communicate with each other using their IP addresses; they must communicate with each other by routing through a public IP address."
+msgstr ""
+
+#: ../../networking/guest_traffic.rst:25
+# 79cb326a48f942949bf3dfe341a3664f
+msgid "See a typical guest traffic setup given below:"
+msgstr ""
+
+#: ../../networking/guest_traffic.rst:27
+# e0ac4742331840b89eef72912ffd2138
+msgid "|guest-traffic-setup.png|"
+msgstr ""
+
+#: ../../networking/guest_traffic.rst:29
+# 685689cd44444e13aefa015c58761ebb
+msgid "Typically, the Management Server automatically creates a virtual router for each network. A virtual router is a special virtual machine that runs on the hosts. Each virtual router in an isolated network has three network interfaces. If multiple public VLAN is used, the router will have multiple public interfaces. Its eth0 interface serves as the gateway for the guest traffic and has the IP address of 10.1.1.1. Its eth1 interface is used by the system to configure the virtual route [...]
+msgstr ""
+
+#: ../../networking/guest_traffic.rst:40
+# c07d5440a8e64d5b912e6e98e6f9d078
+msgid "The virtual router provides DHCP and will automatically assign an IP address for each guest VM within the IP range assigned for the network. The user can manually reconfigure guest VMs to assume different IP addresses."
+msgstr ""
+
+#: ../../networking/guest_traffic.rst:45
+# 360d9d124254479e85292973d6d8e7f9
+msgid "Source NAT is automatically configured in the virtual router to forward outbound traffic for all guest VMs"
+msgstr ""
+
diff --git a/source/adminguide/locale/pot/networking/inter_vlan_routing.pot b/source/adminguide/locale/pot/networking/inter_vlan_routing.pot
new file mode 100644
index 0000000..d7b6b80
--- /dev/null
+++ b/source/adminguide/locale/pot/networking/inter_vlan_routing.pot
@@ -0,0 +1,118 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 
+# This file is distributed under the same license as the Apache CloudStack Administration Documentation package.
+# FIRST AUTHOR <EM...@ADDRESS>, YEAR.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: Apache CloudStack Administration Documentation 4\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2014-06-30 12:52+0200\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EM...@ADDRESS>\n"
+"Language-Team: LANGUAGE <LL...@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#: ../../networking/inter_vlan_routing.rst:18
+# 536a6b6a19a04686832c0c8f3202472a
+msgid "About Inter-VLAN Routing (nTier Apps)"
+msgstr ""
+
+#: ../../networking/inter_vlan_routing.rst:20
+# 01903cae08524fb18fb51475e29cccc5
+msgid "Inter-VLAN Routing (nTier Apps) is the capability to route network traffic between VLANs. This feature enables you to build Virtual Private Clouds (VPC), an isolated segment of your cloud, that can hold multi-tier applications. These tiers are deployed on different VLANs that can communicate with each other. You provision VLANs to the tiers your create, and VMs can be deployed on different tiers. The VLANs are connected to a virtual router, which facilitates communication between  [...]
+msgstr ""
+
+#: ../../networking/inter_vlan_routing.rst:33
+# d835d5a69985471085a5688b045c4e38
+msgid "This feature is supported on XenServer, KVM, and VMware hypervisors."
+msgstr ""
+
+#: ../../networking/inter_vlan_routing.rst:35
+# 7aecd1ac66b84f9cb92b03fea7d5edde
+msgid "The major advantages are:"
+msgstr ""
+
+#: ../../networking/inter_vlan_routing.rst:37
+# dca4c4be393c4d7bbcda75f49ffc8efc
+msgid "The administrator can deploy a set of VLANs and allow users to deploy VMs on these VLANs. A guest VLAN is randomly alloted to an account from a pre-specified set of guest VLANs. All the VMs of a certain tier of an account reside on the guest VLAN allotted to that account."
+msgstr ""
+
+#: ../../networking/inter_vlan_routing.rst:43
+# d5d8b41e126e4b38913d0cf7de1ec29d
+msgid "A VLAN allocated for an account cannot be shared between multiple accounts."
+msgstr ""
+
+#: ../../networking/inter_vlan_routing.rst:45
+# 4e04be2a6cef4fa8973d317232221018
+msgid "The administrator can allow users create their own VPC and deploy the application. In this scenario, the VMs that belong to the account are deployed on the VLANs allotted to that account."
+msgstr ""
+
+#: ../../networking/inter_vlan_routing.rst:49
+# 48018251e76046c4a606035de8d1b4d5
+msgid "Both administrators and users can create multiple VPCs. The guest network NIC is plugged to the VPC virtual router when the first VM is deployed in a tier."
+msgstr ""
+
+#: ../../networking/inter_vlan_routing.rst:53
+# cc50778ecfab43c38af3373511f47072
+msgid "The administrator can create the following gateways to send to or receive traffic from the VMs:"
+msgstr ""
+
+#: ../../networking/inter_vlan_routing.rst:56
+# 5d91169a83a5400b8408b6ce4ccb84f5
+msgid "**VPN Gateway**: For more information, see `\"Creating a VPN gateway for the VPC\" <#creating-a-vpn-gateway-for-the-vpc>`_."
+msgstr ""
+
+#: ../../networking/inter_vlan_routing.rst:59
+# 1f0ed1ecf964455ab40301bdf5ab2dc2
+msgid "**Public Gateway**: The public gateway for a VPC is added to the virtual router when the virtual router is created for VPC. The public gateway is not exposed to the end users. You are not allowed to list it, nor allowed to create any static routes."
+msgstr ""
+
+#: ../../networking/inter_vlan_routing.rst:64
+# b843201a793749bb924d48f21be04e09
+msgid "**Private Gateway**: For more information, see \":ref:`adding-priv-gw-vpc`\"."
+msgstr ""
+
+#: ../../networking/inter_vlan_routing.rst:66
+# a4ac63d4b99a4edd968087d0f622647a
+msgid "Both administrators and users can create various possible destinations-gateway combinations. However, only one gateway of each type can be used in a deployment."
+msgstr ""
+
+#: ../../networking/inter_vlan_routing.rst:70
+# 50735b7154a64b7880f5543c4792b1c0
+msgid "For example:"
+msgstr ""
+
+#: ../../networking/inter_vlan_routing.rst:72
+# bdd41dc64438436aac12d9f1c8d5a8bc
+msgid "**VLANs and Public Gateway**: For example, an application is deployed in the cloud, and the Web application VMs communicate with the Internet."
+msgstr ""
+
+#: ../../networking/inter_vlan_routing.rst:76
+# f2c3b70246534d5aabdd3954a25ba1eb
+msgid "**VLANs, VPN Gateway, and Public Gateway**: For example, an application is deployed in the cloud; the Web application VMs communicate with the Internet; and the database VMs communicate with the on-premise devices."
+msgstr ""
+
+#: ../../networking/inter_vlan_routing.rst:81
+# 7fb2fe01c3484b80a30d4c6edb0b5782
+msgid "The administrator can define Network Access Control List (ACL) on the virtual router to filter the traffic among the VLANs or between the Internet and a VLAN. You can define ACL based on CIDR, port range, protocol, type code (if ICMP protocol is selected) and Ingress/Egress type."
+msgstr ""
+
+#: ../../networking/inter_vlan_routing.rst:87
+# 95cd03acfa2948c682ec51eaf24346be
+msgid "The following figure shows the possible deployment scenarios of a Inter-VLAN setup:"
+msgstr ""
+
+#: ../../networking/inter_vlan_routing.rst:90
+# a9f3216208ba417681d8885848d2a414
+msgid "|mutltier.png|"
+msgstr ""
+
+#: ../../networking/inter_vlan_routing.rst:92
+# 785b1c5286424a3680f6ffa4fa40de5a
+msgid "To set up a multi-tier Inter-VLAN deployment, see \":ref:`configuring-vpc`\"."
+msgstr ""
+
diff --git a/source/adminguide/locale/pot/networking/ip_forwarding_and_firewalling.pot b/source/adminguide/locale/pot/networking/ip_forwarding_and_firewalling.pot
new file mode 100644
index 0000000..009b357
--- /dev/null
+++ b/source/adminguide/locale/pot/networking/ip_forwarding_and_firewalling.pot
@@ -0,0 +1,393 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 
+# This file is distributed under the same license as the Apache CloudStack Administration Documentation package.
+# FIRST AUTHOR <EM...@ADDRESS>, YEAR.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: Apache CloudStack Administration Documentation 4\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2014-06-30 12:52+0200\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EM...@ADDRESS>\n"
+"Language-Team: LANGUAGE <LL...@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:18
+# 3ec46c2d67cb4acc87705b3f0985e5c8
+msgid "IP Forwarding and Firewalling"
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:20
+# 5bb709bf233742ce8f3a83dc5ce7cf26
+msgid "By default, all incoming traffic to the public IP address is rejected. All outgoing traffic from the guests is also blocked by default."
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:23
+# 83f985061e4e4301aa5ce50049ea4565
+msgid "To allow outgoing traffic, follow the procedure in :ref:`egress-fw-rules`."
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:25
+# 1328a8040ae7487b8f7ed1dcaaf5a596
+msgid "To allow incoming traffic, users may set up firewall rules and/or port forwarding rules. For example, you can use a firewall rule to open a range of ports on the public IP address, such as 33 through 44. Then use port forwarding rules to direct traffic from individual ports within that range to specific ports on user VMs. For example, one port forwarding rule could route incoming traffic on the public IP's port 33 to port 100 on one user VM's private IP."
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:35
+# 88ee727310bb4a5789291e8e48578dab
+msgid "Firewall Rules"
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:37
+# 073cb21345c44ce2a3f2ce3446d4ad3a
+msgid "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."
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:43
+# b43e4fc4f43841c9aebd342bbd60b33d
+msgid "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 `\"Adding a Security Group\" <#adding-a-security-group>`_."
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:48
+# 36b1e8acd3ef4b1cb7a7ffd1f60599c5
+msgid "In an advanced zone, you can also create egress firewall rules by using the virtual router. For more information, see \":ref:`egress-fw-rules`\"."
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:51
+# 2aeb084c075b4451b0911c2a6baf0f84
+msgid "Firewall rules can be created using the Firewall tab in the Management Server UI. This tab is not displayed by default when CloudStack is installed. To display the Firewall tab, the CloudStack administrator must set the global configuration parameter firewall.rule.ui.enabled to \"true.\""
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:57
+# e1408eeb730f4709bbba8852f79807fd
+msgid "To create a firewall rule:"
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:59
+#: ../../networking/ip_forwarding_and_firewalling.rst:132
+#: ../../networking/ip_forwarding_and_firewalling.rst:245
+# 098b22043ec643559c039b39aa24d618
+# f62479b013c241a791c42b8843bd140d
+# c384f1b44804485fba23fe018c16683e
+msgid "Log in to the CloudStack UI as an administrator or end user."
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:61
+#: ../../networking/ip_forwarding_and_firewalling.rst:134
+# a633160d3ee343639365b9067af58eb1
+# c6c7495d464a4262ace3361c7cce9b5b
+msgid "In the left navigation, choose Network."
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:63
+# ff56e69810c34ee4a08280a7ef06cfbb
+msgid "Click the name of the network where you want to work with."
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:65
+# d546be88025a4254b8eecf1f0b16bdf0
+msgid "Click View IP Addresses."
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:67
+# 0c60a7fde5644f9188c0bf190c166890
+msgid "Click the IP address you want to work with."
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:69
+# 0e0775a902554fa68fc54157ed73ed0a
+msgid "Click the Configuration tab and fill in the following values."
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:71
+# 8bb21f2deca7442683f782de4a83935f
+msgid "**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."
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:76
+# 4cb05fbe28ae408a8df34014da711575
+msgid "**Protocol**: The communication protocol in use on the opened port(s)."
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:79
+# e59d4d2a187f4510a91409fac5cfb51c
+msgid "**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"
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:83
+# 3274875afce44bbe9d7017bb4e2fc2b2
+msgid "**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"
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:88
+#: ../../networking/ip_forwarding_and_firewalling.rst:163
+#: ../../networking/ip_forwarding_and_firewalling.rst:276
+# 41821a610d844daf8255026b71299059
+# 1d39fcb3a5e34d769f89885db9866836
+# 2319658c89b74a0294ce8f0a253a4d53
+msgid "Click Add."
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:94
+# eec2e0a57feb4eca85c58ac1b58b228b
+msgid "Egress Firewall Rules in an Advanced Zone"
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:96
+# 3bae6d1e0fb543beaeb466c40aeddfc3
+msgid "The egress traffic originates from a private network to a public network, such as the Internet. By default, the egress traffic is blocked in default network offerings, so no outgoing traffic is allowed from a guest network to the Internet. However, you can control the egress traffic in an Advanced zone by creating egress firewall rules. When an egress firewall rule is applied, the traffic specific to the rule is allowed and the remaining traffic is blocked. When all the firewall r [...]
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:107
+# 80fbdba2a681463894376f620458c160
+msgid "Prerequisites and Guidelines"
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:109
+# 998ae537c5664319b836e769ab967fc3
+msgid "Consider the following scenarios to apply egress firewall rules:"
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:111
+# 18a68e97f28f4f7898b92513d34e5e26
+msgid "Egress firewall rules are supported on Juniper SRX and virtual router."
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:114
+# a4eaae6cb4474e5a8182092404f48116
+msgid "The egress firewall rules are not supported on shared networks."
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:116
+# 85bdd2e7a708485bae147bfa93cdcb1b
+msgid "Allow the egress traffic from specified source CIDR. The Source CIDR is part of guest network CIDR."
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:119
+# d9af348ce95e47a0bae91a55488b1155
+msgid "Allow the egress traffic with protocol TCP,UDP,ICMP, or ALL."
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:121
+# 786d85af2e334cf5a8a25fc59dde7cb5
+msgid "Allow the egress traffic with protocol and destination port range. The port range is specified for TCP, UDP or for ICMP type and code."
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:124
+# 8d9e5fa49cb648a6ad0b917f06176014
+msgid "The default policy is Allow for the new network offerings, whereas on upgrade existing network offerings with firewall service providers will have the default egress policy Deny."
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:130
+# ee1ee0417255469abce66dbfd40f9611
+msgid "Configuring an Egress Firewall Rule"
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:136
+# 4d43b047c25a4605acc888b025d376aa
+msgid "In Select view, choose Guest networks, then click the Guest network you want."
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:139
+# 4c11dfc739f94ce0995b7c7bdf566e5d
+msgid "To add an egress rule, click the Egress rules tab and fill out the following fields to specify what type of traffic is allowed to be sent out of VM instances in this guest network:"
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:143
+# a476fe8da41b43168b89c7b558afcb48
+msgid "|egress-firewall-rule.png|"
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:145
+# d56527f1ac864c5c9d47df9e55c225cf
+msgid "**CIDR**: (Add by CIDR only) To send traffic only to the IP addresses within a particular address block, enter a CIDR or a comma-separated list of CIDRs. The CIDR is the base IP address of the destination. For example, 192.168.0.0/22. To allow all CIDRs, set to 0.0.0.0/0."
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:151
+# c1e8fac9fa8046d8a9315511c011542e
+msgid "**Protocol**: The networking protocol that VMs uses to send outgoing traffic. The TCP and UDP protocols are typically used for data exchange and end-user communications. The ICMP protocol is typically used to send error messages or network monitoring data."
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:156
+# 6b9d46d4c88d48c98d3fa4fcceb60e29
+msgid "**Start Port, End Port**: (TCP, UDP only) A range of listening ports that are the destination for the outgoing traffic. If you are opening a single port, use the same number in both fields."
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:160
+# 17c266c56f194132a6fc948f3142e4bc
+msgid "**ICMP Type, ICMP Code**: (ICMP only) The type of message and error code that are sent."
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:167
+# f0100304289f4a67b01e8f6c52976a10
+msgid "Configuring the Default Egress Policy"
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:169
+# a802326f92404392beacd9675985c106
+msgid "The default egress policy for Isolated guest network is configured by using Network offering. Use the create network offering option to determine whether the default policy should be block or allow all the traffic to the public network from a guest network. Use this network offering to create the network. If no policy is specified, by default all the traffic is allowed from the guest network that you create by using this network offering."
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:177
+# 9b5e480b6757449ab8272d3e7a691110
+msgid "You have two options: Allow and Deny."
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:180
+# 9b8d4463d6024d8589cc801658fa7bab
+msgid "Allow"
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:182
+# 01d29e0665f84d548d9f41399d9258d8
+msgid "If you select Allow for a network offering, by default egress traffic is allowed. However, when an egress rule is configured for a guest network, rules are applied to block the specified traffic and rest are allowed. If no egress rules are configured for the network, egress traffic is accepted."
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:189
+# 63816b9551f04933aa99e27cc3dc34f1
+msgid "Deny"
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:191
+# 1952d7735fb746a6834bbdeed4c1eaa9
+msgid "If you select Deny for a network offering, by default egress traffic for the guest network is blocked. However, when an egress rules is configured for a guest network, rules are applied to allow the specified traffic. While implementing a guest network, CloudStack adds the firewall egress rule specific to the default egress policy for the guest network."
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:198
+# 238db98415e74782937deddd3970b285
+msgid "This feature is supported only on virtual router and Juniper SRX."
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:200
+# e460df960d61405db56e64d21a8c43d7
+msgid "Create a network offering with your desirable default egress policy:"
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:202
+# 5271ad0a1d4a4a27aa5597b044b42acf
+msgid "Log in with admin privileges to the CloudStack UI."
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:204
+# fd49a59627284ffda66fef7096eaa709
+msgid "In the left navigation bar, click Service Offerings."
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:206
+# 7fce8b96f6e64727bb6063766c828bdd
+msgid "In Select Offering, choose Network Offering."
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:208
+# ef8895c197ff4343b04aecc73b5a9294
+msgid "Click Add Network Offering."
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:210
+# abb73d0d766d4d32a4bbe32137193cad
+msgid "In the dialog, make necessary choices, including firewall provider."
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:213
+# 932c30480a1f4e3ea92f06ba4296ae45
+msgid "In the Default egress policy field, specify the behaviour."
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:215
+# 41d012a83e774bdeaeac42e5b44d851c
+msgid "Click OK."
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:217
+# 5a1192bc5c8a4c3c930879e56c5d58bb
+msgid "Create an isolated network by using this network offering."
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:219
+# 3918ff66d4914376a4707b9db470a027
+msgid "Based on your selection, the network will have the egress public traffic blocked or allowed."
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:224
+# 29ffedbd547e431f95d82b075df5ea66
+msgid "Port Forwarding"
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:226
+# d9efd9df178e4f7c8d81b2ba24a9fdbb
+msgid "A port forward service is a set of port forwarding rules that define a policy. A port forward service is then applied to one or more guest VMs. The guest VM then has its inbound network access managed according to the policy defined by the port forwarding service. 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 to be forwarded."
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:234
+# ae4f5d3e4bc24f8584c17c3057688144
+msgid "A guest VM can be in any number of port forward services. Port forward services can be defined but have no members. If a guest VM is part of more than one network, port forwarding rules will function only if they are defined on the default network"
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:239
+# 89ce910349884d8ea8a7b4f6aee10613
+msgid "You cannot use port forwarding 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 Security Groups."
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:243
+# 263627f6e1de45999d0e9ab68c8a1a2d
+msgid "To set up port forwarding:"
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:247
+# 41c9b9f2473e4b5aa0d8ea3c54e45b1b
+msgid "If you have not already done so, add a public IP address range to a zone in CloudStack. See Adding a Zone and Pod in the Installation Guide."
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:251
+# 2c98fbd961df4ef28a276b3ccf1d53c0
+msgid "Add one or more VM instances to CloudStack."
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:253
+# 17a544cc6c8a42cbaef47575f1029173
+msgid "In the left navigation bar, click Network."
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:255
+# ade84b4f63694fadbe6c835b52ba796f
+msgid "Click the name of the guest network where the VMs are running."
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:257
+# 48ab8bf9d7e04ca7a13eaf58eeead278
+msgid "Choose an existing IP address or acquire a new IP address. See `\"Acquiring a New IP Address\" <#acquiring-a-new-ip-address>`_. Click the name of the IP address in the list."
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:261
+# da392889cd304ce8973c2b4b8341665b
+msgid "Click the Configuration tab."
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:263
+# 4d02af0497b544d89616ff1ddf286767
+msgid "In the Port Forwarding node of the diagram, click View All."
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:265
+# ee9101e2c97447d4b23f89177c60e7ab
+msgid "Fill in the following:"
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:267
+# e9d9402255ae405781f85b32409d3654
+msgid "**Public Port**: The port to which public traffic will be addressed on the IP address you acquired in the previous step."
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:270
+# bf8d351e8ca649ca9931311f402ea7bc
+msgid "**Private Port**: The port on which the instance is listening for forwarded public traffic."
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:273
+# 5140efc173fd46e194d6c4827a8a67fc
+msgid "**Protocol**: The communication protocol in use between the two ports"
+msgstr ""
+
diff --git a/source/adminguide/locale/pot/networking/ip_load_balancing.pot b/source/adminguide/locale/pot/networking/ip_load_balancing.pot
new file mode 100644
index 0000000..4d79eb1
--- /dev/null
+++ b/source/adminguide/locale/pot/networking/ip_load_balancing.pot
@@ -0,0 +1,48 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 
+# This file is distributed under the same license as the Apache CloudStack Administration Documentation package.
+# FIRST AUTHOR <EM...@ADDRESS>, YEAR.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: Apache CloudStack Administration Documentation 4\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2014-06-30 12:52+0200\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EM...@ADDRESS>\n"
+"Language-Team: LANGUAGE <LL...@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#: ../../networking/ip_load_balancing.rst:18
+# 974ac2a4e2dd4641920f5361833b3e12
+msgid "IP Load Balancing"
+msgstr ""
+
+#: ../../networking/ip_load_balancing.rst:20
+# 7eaede5161a04e0cbb6a4b15fc2de3b2
+msgid "The user may choose to associate the same public IP for multiple guests. CloudStack implements a TCP-level load balancer with the following policies."
+msgstr ""
+
+#: ../../networking/ip_load_balancing.rst:24
+# 8c044fa0f1714d63815a08d7a658b08d
+msgid "Round-robin"
+msgstr ""
+
+#: ../../networking/ip_load_balancing.rst:26
+# 6732c79a9ecf4eec91f6ddea4d55833a
+msgid "Least connection"
+msgstr ""
+
+#: ../../networking/ip_load_balancing.rst:28
+# 28c3b6fa228545e382ed84cceaf1666a
+msgid "Source IP"
+msgstr ""
+
+#: ../../networking/ip_load_balancing.rst:30
+# 0eac6f2afde349909f9ee8d0148a99b6
+msgid "This is similar to port forwarding but the destination may be multiple IP addresses."
+msgstr ""
+
diff --git a/source/adminguide/locale/pot/networking/ip_reservation_in_guest_networks.pot b/source/adminguide/locale/pot/networking/ip_reservation_in_guest_networks.pot
new file mode 100644
index 0000000..4d28e10
--- /dev/null
+++ b/source/adminguide/locale/pot/networking/ip_reservation_in_guest_networks.pot
@@ -0,0 +1,238 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 
+# This file is distributed under the same license as the Apache CloudStack Administration Documentation package.
+# FIRST AUTHOR <EM...@ADDRESS>, YEAR.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: Apache CloudStack Administration Documentation 4\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2014-06-30 12:52+0200\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EM...@ADDRESS>\n"
+"Language-Team: LANGUAGE <LL...@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#: ../../networking/ip_reservation_in_guest_networks.rst:18
+# 25e21d9bd50e4db29764c09ec3255ea1
+msgid "IP Reservation in Isolated Guest Networks"
+msgstr ""
+
+#: ../../networking/ip_reservation_in_guest_networks.rst:20
+# f043acb1e27b49aebecf48876dca90d4
+msgid "In isolated guest networks, a part of the guest IP address space can be reserved for non-CloudStack VMs or physical servers. To do so, you configure a range of Reserved IP addresses by specifying the CIDR when a guest network is in Implemented state. If your customers wish to have non-CloudStack controlled VMs or physical servers on the same network, they can share a part of the IP address space that is primarily provided to the guest network."
+msgstr ""
+
+#: ../../networking/ip_reservation_in_guest_networks.rst:28
+# fe77cb19c33a475f9389f57e62e466e0
+msgid "In an Advanced zone, an IP address range or a CIDR is assigned to a network when the network is defined. The CloudStack virtual router acts as the DHCP server and uses CIDR for assigning IP addresses to the guest VMs. If you decide to reserve CIDR for non-CloudStack purposes, you can specify a part of the IP address range or the CIDR that should only be allocated by the DHCP service of the virtual router to the guest VMs created in CloudStack. The remaining IPs in that network are [...]
+msgstr ""
+
+#: ../../networking/ip_reservation_in_guest_networks.rst:43
+# 9428ab05bfce48cb9dce92078998854c
+msgid "IP Reservation Considerations"
+msgstr ""
+
+#: ../../networking/ip_reservation_in_guest_networks.rst:45
+# 5780d0b48e6f44cbb972018a31489ebb
+msgid "Consider the following before you reserve an IP range for non-CloudStack machines:"
+msgstr ""
+
+#: ../../networking/ip_reservation_in_guest_networks.rst:48
+# cc50e370af0c450588c711e282c0ac93
+msgid "IP Reservation is supported only in Isolated networks."
+msgstr ""
+
+#: ../../networking/ip_reservation_in_guest_networks.rst:50
+# 9543f099f9de4fc3a8a815cd3cb04f40
+msgid "IP Reservation can be applied only when the network is in Implemented state."
+msgstr ""
+
+#: ../../networking/ip_reservation_in_guest_networks.rst:53
+# c7bc13975b37474299e4a7a65c56ed75
+msgid "No IP Reservation is done by default."
+msgstr ""
+
+#: ../../networking/ip_reservation_in_guest_networks.rst:55
+# f7a970b25ef94f48bc75a5c8a5fd0a0c
+msgid "Guest VM CIDR you specify must be a subset of the network CIDR."
+msgstr ""
+
+#: ../../networking/ip_reservation_in_guest_networks.rst:57
+# a96a64591c4d498ca7c95b1458def6f3
+msgid "Specify a valid Guest VM CIDR. IP Reservation is applied only if no active IPs exist outside the Guest VM CIDR."
+msgstr ""
+
+#: ../../networking/ip_reservation_in_guest_networks.rst:60
+# 0710411bb18c4764970dffcc49fe5dab
+msgid "You cannot apply IP Reservation if any VM is alloted with an IP address that is outside the Guest VM CIDR."
+msgstr ""
+
+#: ../../networking/ip_reservation_in_guest_networks.rst:63
+# ba005fe1c84e4e5d8d8b2f2cbd904deb
+msgid "To reset an existing IP Reservation, apply IP reservation by specifying the value of network CIDR in the CIDR field."
+msgstr ""
+
+#: ../../networking/ip_reservation_in_guest_networks.rst:66
+# 23bef4e190a54c2298a52b3acb439c57
+msgid "For example, the following table describes three scenarios of guest network creation:"
+msgstr ""
+
+#: ../../networking/ip_reservation_in_guest_networks.rst:70
+# fd80ccd9ee7947c6a41f35a77766ba87
+msgid "Case"
+msgstr ""
+
+#: ../../networking/ip_reservation_in_guest_networks.rst:70
+# 1b0d9124efce41c8bf2ff9c04f471053
+msgid "CIDR"
+msgstr ""
+
+#: ../../networking/ip_reservation_in_guest_networks.rst:70
+# 340cf6747d6449b09015c49437828468
+msgid "Network CIDR"
+msgstr ""
+
+#: ../../networking/ip_reservation_in_guest_networks.rst:70
+# ca9e89e3707343c6a6bb2e2c52dc4acd
+msgid "Reserved IP Range for Non-CloudStack VMs"
+msgstr ""
+
+#: ../../networking/ip_reservation_in_guest_networks.rst:70
+# e1395f7f735643f98e49f71acb302533
+msgid "Description"
+msgstr ""
+
+#: ../../networking/ip_reservation_in_guest_networks.rst:72
+# bfc721eb783042dbbd4049d97eeae50c
+msgid "1"
+msgstr ""
+
+#: ../../networking/ip_reservation_in_guest_networks.rst:72
+#: ../../networking/ip_reservation_in_guest_networks.rst:73
+#: ../../networking/ip_reservation_in_guest_networks.rst:76
+# 07110191079642298d8d53f83f4a6fe7
+# a0e61e48b84a4bb297fead377ce043cf
+# d64231917df74c5189732a5fedd1d141
+msgid "10.1.1.0/24"
+msgstr ""
+
+#: ../../networking/ip_reservation_in_guest_networks.rst:72
+#: ../../networking/ip_reservation_in_guest_networks.rst:72
+#: ../../networking/ip_reservation_in_guest_networks.rst:76
+#: ../../networking/ip_reservation_in_guest_networks.rst:76
+# 865ea8d88306424bab506a500520c22e
+# 184b1eac870b483f910546a5d5b37906
+# 70f4868471d54ac882b8093eb1db9f74
+# 3c040050888741f09b3cee5a8482aca4
+msgid "None"
+msgstr ""
+
+#: ../../networking/ip_reservation_in_guest_networks.rst:72
+# 24e526351c7b4686b16e030bc869d399
+msgid "No IP Reservation."
+msgstr ""
+
+#: ../../networking/ip_reservation_in_guest_networks.rst:73
+# 81f560cf3b4c47bbb2b781add102de88
+msgid "2"
+msgstr ""
+
+#: ../../networking/ip_reservation_in_guest_networks.rst:73
+# 725f92aed0d44be3bb5865f246acc29d
+msgid "10.1.1.0/26"
+msgstr ""
+
+#: ../../networking/ip_reservation_in_guest_networks.rst:73
+# 02e4012c8ce94d95a0c5e4d5088637fd
+msgid "10.1.1.64 to 10.1.1.254"
+msgstr ""
+
+#: ../../networking/ip_reservation_in_guest_networks.rst:73
+# 8fe36bed92d2475bbdd0fa903eb8c54b
+msgid "IP Reservation configured by the UpdateNetwork API with guestvmcidr=10.1.1.0/26 or enter 10.1.1.0/26 in the CIDR field in the UI."
+msgstr ""
+
+#: ../../networking/ip_reservation_in_guest_networks.rst:76
+# e2c363737b654228a0ac0581ba4c55c8
+msgid "3"
+msgstr ""
+
+#: ../../networking/ip_reservation_in_guest_networks.rst:76
+# 139e9ad2489d40738198ebfac4b14c45
+msgid "Removing IP Reservation by the UpdateNetwork API with guestvmcidr=10.1.1.0/24 or enter 10.1.1.0/24 in the CIDR field in the UI."
+msgstr ""
+
+#: ../../networking/ip_reservation_in_guest_networks.rst:83
+# 43bbd9a15792420cb8b1e694ad792cf2
+msgid "Limitations"
+msgstr ""
+
+#: ../../networking/ip_reservation_in_guest_networks.rst:85
+# 1ed6f796d3f04ed0b5c96512bc673c25
+msgid "The IP Reservation is not supported if active IPs that are found outside the Guest VM CIDR."
+msgstr ""
+
+#: ../../networking/ip_reservation_in_guest_networks.rst:88
+# 28ed30440a3543f6b7744261f3f5c2e0
+msgid "Upgrading network offering which causes a change in CIDR (such as upgrading an offering with no external devices to one with external devices) IP Reservation becomes void if any. Reconfigure IP Reservation in the new re-implemeted network."
+msgstr ""
+
+#: ../../networking/ip_reservation_in_guest_networks.rst:95
+# f9aacfd3f1a94c7c8d3ca0910da962a9
+msgid "Best Practices"
+msgstr ""
+
+#: ../../networking/ip_reservation_in_guest_networks.rst:97
+# c5d0950bef8a49ce9b373d64fcf22b86
+msgid "Apply IP Reservation to the guest network as soon as the network state changes to Implemented. If you apply reservation soon after the first guest VM is deployed, lesser conflicts occurs while applying reservation."
+msgstr ""
+
+#: ../../networking/ip_reservation_in_guest_networks.rst:104
+# 636d85b86d5a460788a233fd1cb49014
+msgid "Reserving an IP Range"
+msgstr ""
+
+#: ../../networking/ip_reservation_in_guest_networks.rst:106
+# 34eb58849cb141e9898291a434cc05ba
+msgid "Log in to the CloudStack UI as an administrator or end user."
+msgstr ""
+
+#: ../../networking/ip_reservation_in_guest_networks.rst:108
+# 3dc484e1bd5145259125fe0fcf8ccf8c
+msgid "In the left navigation, choose Network."
+msgstr ""
+
+#: ../../networking/ip_reservation_in_guest_networks.rst:110
+# e4559a4e7ddf4812890314b955dae344
+msgid "Click the name of the network you want to modify."
+msgstr ""
+
+#: ../../networking/ip_reservation_in_guest_networks.rst:112
+# 9119b8d7ea884da4b996f8a191d30e0b
+msgid "In the Details tab, click Edit. |ip-edit-icon.png|"
+msgstr ""
+
+#: ../../networking/ip_reservation_in_guest_networks.rst:114
+# 31eaf6bfc27e465e950da4b920fbad80
+msgid "The CIDR field changes to editable one."
+msgstr ""
+
+#: ../../networking/ip_reservation_in_guest_networks.rst:116
+# f29831c8666d45218af0ae6769e46fff
+msgid "In CIDR, specify the Guest VM CIDR."
+msgstr ""
+
+#: ../../networking/ip_reservation_in_guest_networks.rst:118
+# 41acec1236df4ddbad427f23127244b1
+msgid "Click Apply."
+msgstr ""
+
+#: ../../networking/ip_reservation_in_guest_networks.rst:120
+# 8213a6fd8f414bd2b710a4ee77b167ae
+msgid "Wait for the update to complete. The Network CIDR and the Reserved IP Range are displayed on the Details page."
+msgstr ""
+
diff --git a/source/adminguide/locale/pot/networking/isolation_in_advanced_zone_with_vlan.pot b/source/adminguide/locale/pot/networking/isolation_in_advanced_zone_with_vlan.pot
new file mode 100644
index 0000000..1839104
--- /dev/null
+++ b/source/adminguide/locale/pot/networking/isolation_in_advanced_zone_with_vlan.pot
@@ -0,0 +1,273 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 
+# This file is distributed under the same license as the Apache CloudStack Administration Documentation package.
+# FIRST AUTHOR <EM...@ADDRESS>, YEAR.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: Apache CloudStack Administration Documentation 4\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2014-06-30 12:52+0200\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EM...@ADDRESS>\n"
+"Language-Team: LANGUAGE <LL...@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:18
+# 2ce5e59640934ab387652df180ce1583
+msgid "Isolation in Advanced Zone Using Private VLAN"
+msgstr ""
+
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:20
+# 813ada1771994469abac6b243cbc4ed6
+msgid "Isolation of guest traffic in shared networks can be achieved by using Private VLANs (PVLAN). PVLANs provide Layer 2 isolation between ports within the same VLAN. In a PVLAN-enabled shared network, a user VM cannot reach other user VM though they can reach the DHCP server and gateway, this would in turn allow users to control traffic within a network and help them deploy multiple applications without communication between application as well as prevent communication with other use [...]
+msgstr ""
+
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:29
+# 1f6fb3f08ede4dbcbd7c9017afd047dd
+msgid "Isolate VMs in a shared networks by using Private VLANs."
+msgstr ""
+
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:31
+# c578b86e668046b18652e81289fd1811
+msgid "Supported on KVM, XenServer, and VMware hypervisors"
+msgstr ""
+
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:33
+# f410d2d58c4b4e91b95fec05d57cf0b8
+msgid "PVLAN-enabled shared network can be a part of multiple networks of a guest VM."
+msgstr ""
+
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:38
+# 23d9d81e853644d8a8e311853c02a801
+msgid "About Private VLAN"
+msgstr ""
+
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:40
+# a83e1c8b0ee2433b8776507d78fdd2b4
+msgid "In an Ethernet switch, a VLAN is a broadcast domain where hosts can establish direct communication with each another at Layer 2. Private VLAN is designed as an extension of VLAN standard to add further segmentation of the logical broadcast domain. A regular VLAN is a single broadcast domain, whereas a private VLAN partitions a larger VLAN broadcast domain into smaller sub-domains. A sub-domain is represented by a pair of VLANs: a Primary VLAN and a Secondary VLAN. The original VLA [...]
+msgstr ""
+
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:53
+# 4b8abf8fe1534c228333ad081037a150
+msgid "Three types of ports exist in a private VLAN domain, which essentially determine the behaviour of the participating hosts. Each ports will have its own unique set of rules, which regulate a connected host's ability to communicate with other connected host within the same private VLAN domain. Configure each host that is part of a PVLAN pair can be by using one of these three port designation:"
+msgstr ""
+
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:60
+# d369217099d04739b0c778e20ac02897
+msgid "**Promiscuous**: A promiscuous port can communicate with all the interfaces, including the community and isolated host ports that belong to the secondary VLANs. In Promiscuous mode, hosts are connected to promiscuous ports and are able to communicate directly with resources on both primary and secondary VLAN. Routers, DHCP servers, and other trusted devices are typically attached to promiscuous ports."
+msgstr ""
+
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:68
+# 1e0c762b123d404eaedebd33003ad75b
+msgid "**Isolated VLANs**: The ports within an isolated VLAN cannot communicate with each other at the layer-2 level. The hosts that are connected to Isolated ports can directly communicate only with the Promiscuous resources. If your customer device needs to have access only to a gateway router, attach it to an isolated port."
+msgstr ""
+
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:74
+# 15e3128ebacd47afb6aa943d0f2a5df1
+msgid "**Community VLANs**: The ports within a community VLAN can communicate with each other and with the promiscuous ports, but they cannot communicate with the ports in other communities at the layer-2 level. In a Community mode, direct communication is permitted only with the hosts in the same community and those that are connected to the Primary PVLAN in promiscuous mode. If your customer has two devices that need to be isolated from other customers' devices, but to be able to commu [...]
+msgstr ""
+
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:84
+# 6a977183f6864375ada79a287e63bab3
+msgid "For further reading:"
+msgstr ""
+
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:86
+# ca791914bab54854b0b9c5cfdbb20be8
+msgid "`Understanding Private VLANs <http://www.cisco.com/en/US/docs/switches/lan/catalyst3750/software/release/12.2_25_see/configuration/guide/swpvlan.html#wp1038379>`_"
+msgstr ""
+
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:89
+# e676f05feb9a46d6974a4ed7048edad2
+msgid "`Cisco Systems' Private VLANs: Scalable Security in a Multi-Client Environment <http://tools.ietf.org/html/rfc5517>`_"
+msgstr ""
+
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:92
+# d5429c82db8a47aa82c6bf7602605f93
+msgid "`Private VLAN (PVLAN) on vNetwork Distributed Switch - Concept Overview (1010691) <http://kb.vmware.com>`_"
+msgstr ""
+
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:97
+# ad67b66852ee445b847bec89936c0d02
+msgid "Prerequisites"
+msgstr ""
+
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:99
+# 1f2367cd590b456b9590a9b2616c8ad5
+msgid "Use a PVLAN supported switch."
+msgstr ""
+
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:101
+# f2c1161babac465c93d8ff531d97174d
+msgid "See `Private VLAN Catalyst Switch Support Matrix <http://www.cisco.com/en/US/products/hw/switches/ps708/products_tech_note09186a0080094830.shtml>`_ for more information."
+msgstr ""
+
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:105
+# d6805374b5244b3da5f5a39bbb521739
+msgid "All the layer 2 switches, which are PVLAN-aware, are connected to each other, and one of them is connected to a router. All the ports connected to the host would be configured in trunk mode. Open Management VLAN, Primary VLAN (public) and Secondary Isolated VLAN ports. Configure the switch port connected to the router in PVLAN promiscuous trunk mode, which would translate an isolated VLAN to primary VLAN for the PVLAN-unaware router."
+msgstr ""
+
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:113
+# 3afd52bf2fa3442b8f0721d8bca53715
+msgid "Note that only Cisco Catalyst 4500 has the PVLAN promiscuous trunk mode to connect both normal VLAN and PVLAN to a PVLAN-unaware switch. For the other Catalyst PVLAN support switch, connect the switch to upper switch by using cables, one each for a PVLAN pair."
+msgstr ""
+
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:118
+# 5ce2b463414844099564cd171152b994
+msgid "Configure private VLAN on your physical switches out-of-band."
+msgstr ""
+
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:120
+# 2cd1aebdb79742a3ab786e439ef69d89
+msgid "Before you use PVLAN on XenServer and KVM, enable Open vSwitch (OVS)."
+msgstr ""
+
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:123
+# 23029ff5d87847c3b9a551d1755aae1a
+msgid "OVS on XenServer and KVM does not support PVLAN natively. Therefore, CloudStack managed to simulate PVLAN on OVS for XenServer and KVM by modifying the flow table."
+msgstr ""
+
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:129
+# 1ab529fe7a53485da31a8085c5fc8181
+msgid "Creating a PVLAN-Enabled Guest Network"
+msgstr ""
+
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:131
+# 73811e0470e04b63a31d32549a8c882b
+msgid "Log in to the CloudStack UI as administrator."
+msgstr ""
+
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:133
+# f987d4525be34ae986962e374a48197f
+msgid "In the left navigation, choose Infrastructure."
+msgstr ""
+
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:135
+# 81a7cad61d0c43e3989e9742e6efb902
+msgid "On Zones, click View More."
+msgstr ""
+
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:137
+# 62eb1c2209d34440987b38dc999dad75
+msgid "Click the zone to which you want to add a guest network."
+msgstr ""
+
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:139
+# aeaece1bb557450383b2b0c0930b8d39
+msgid "Click the Physical Network tab."
+msgstr ""
+
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:141
+# bdccf5bb73ce4a58b074c7db9f09db19
+msgid "Click the physical network you want to work with."
+msgstr ""
+
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:143
+# d325d3d79e0e41fd9ce93131ae2ea76a
+msgid "On the Guest node of the diagram, click Configure."
+msgstr ""
+
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:145
+# 3254ff32eecc4e9b9ac57fc4f2219acd
+msgid "Click the Network tab."
+msgstr ""
+
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:147
+# fdd056f25bee447e98028c9301071fd7
+msgid "Click Add guest network."
+msgstr ""
+
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:149
+# f58f17bd25284897abbe7df71fc2c3fb
+msgid "The Add guest network window is displayed."
+msgstr ""
+
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:151
+# 5e421fb492504766a709b728f4fc51e5
+msgid "Specify the following:"
+msgstr ""
+
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:153
+# 606686347ca84fbc9a83c5f46c31d8ea
+msgid "**Name**: The name of the network. This will be visible to the user."
+msgstr ""
+
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:156
+# 73bbe5e4075e43f39b388b8b267c5401
+msgid "**Description**: The short description of the network that can be displayed to users."
+msgstr ""
+
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:159
+# 17a0fe7f48cc4af3bbe7b8e52b6f6d1b
+msgid "**VLAN ID**: The unique ID of the VLAN."
+msgstr ""
+
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:161
+# 1656d47de54d42a788bc34e0a0c5f2e4
+msgid "**Secondary Isolated VLAN ID**: The unique ID of the Secondary Isolated VLAN."
+msgstr ""
+
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:164
+# 22e09670bce14054b1c11ce5ff049ba5
+msgid "For the description on Secondary Isolated VLAN, see `About Private VLAN\" <#about-private-vlan>`_."
+msgstr ""
+
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:167
+# 38765c8ae24048dba72826d07d096afe
+msgid "**Scope**: The available scopes are Domain, Account, Project, and All."
+msgstr ""
+
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:170
+# 90706772c0084832b86742ce99f99d6e
+msgid "**Domain**: Selecting Domain limits the scope of this guest network to the domain you specify. The network will not be available for other domains. If you select Subdomain Access, the guest network is available to all the sub domains within the selected domain."
+msgstr ""
+
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:176
+# 7e174e9b956f4f2784d5196f1a30439f
+msgid "**Account**: The account for which the guest network is being created for. You must specify the domain the account belongs to."
+msgstr ""
+
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:180
+# d8216708afb2490c97e3cca13b2752dd
+msgid "**Project**: The project for which the guest network is being created for. You must specify the domain the project belongs to."
+msgstr ""
+
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:184
+# 3aa0f96be4f84d1bae1f1744b108dff8
+msgid "**All**: The guest network is available for all the domains, account, projects within the selected zone."
+msgstr ""
+
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:187
+# 339b47c6f0f94ca4a221c0f592e92d5b
+msgid "**Network Offering**: If the administrator has configured multiple network offerings, select the one you want to use for this network."
+msgstr ""
+
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:191
+# ae2111debd664f179fe8eb3b251587ff
+msgid "**Gateway**: The gateway that the guests should use."
+msgstr ""
+
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:193
+# df6c332c5f7e427d867dcef1784c0731
+msgid "**Netmask**: The netmask in use on the subnet the guests will use."
+msgstr ""
+
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:195
+# 5331fd382d74450c957ad9e5fa46a095
+msgid "**IP Range**: A range of IP addresses that are accessible from the Internet and are assigned to the guest VMs."
+msgstr ""
+
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:198
+# 6be7da6ede894331ad2082717f19c89d
+msgid "**Network Domain**: A custom DNS suffix at the level of a network. If you want to assign a special domain name to the guest VM network, specify a DNS suffix."
+msgstr ""
+
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:202
+# 0f106d1db97249348138b9cf76182524
+msgid "Click OK to confirm."
+msgstr ""
+
diff --git a/source/adminguide/locale/pot/networking/multiple_guest_networks.pot b/source/adminguide/locale/pot/networking/multiple_guest_networks.pot
new file mode 100644
index 0000000..fa2f693
--- /dev/null
+++ b/source/adminguide/locale/pot/networking/multiple_guest_networks.pot
@@ -0,0 +1,312 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 
+# This file is distributed under the same license as the Apache CloudStack Administration Documentation package.
+# FIRST AUTHOR <EM...@ADDRESS>, YEAR.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: Apache CloudStack Administration Documentation 4\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2014-06-30 12:52+0200\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EM...@ADDRESS>\n"
+"Language-Team: LANGUAGE <LL...@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#: ../../networking/multiple_guest_networks.rst:18
+# cbc2c710bdfe4a52822f6acf8381d1dd
+msgid "Using Multiple Guest Networks"
+msgstr ""
+
+#: ../../networking/multiple_guest_networks.rst:20
+# 43824860271641cabc92b4e2fea91b0d
+msgid "In zones that use advanced networking, additional networks for guest traffic may be added at any time after the initial installation. You can also customize the domain name associated with the network by specifying a DNS suffix for each network."
+msgstr ""
+
+#: ../../networking/multiple_guest_networks.rst:25
+# e7a7a8ebce174e439d282d7c86c23ffc
+msgid "A VM's networks are defined at VM creation time. A VM cannot add or remove networks after it has been created, although the user can go into the guest and remove the IP address from the NIC on a particular network."
+msgstr ""
+
+#: ../../networking/multiple_guest_networks.rst:30
+# c1facfd27f164a849bd7151e92129d58
+msgid "Each VM has just one default network. The virtual router's DHCP reply will set the guest's default gateway as that for the default network. Multiple non-default networks may be added to a guest in addition to the single, required default network. The administrator can control which networks are available as the default network."
+msgstr ""
+
+#: ../../networking/multiple_guest_networks.rst:36
+# 008bbd9e609541888208d792dda845fd
+msgid "Additional networks can either be available to all accounts or be assigned to a specific account. Networks that are available to all accounts are zone-wide. Any user with access to the zone can create a VM with access to that network. These zone-wide networks provide little or no isolation between guests.Networks that are assigned to a specific account provide strong isolation."
+msgstr ""
+
+#: ../../networking/multiple_guest_networks.rst:45
+# e8b12ba98b314fcca6f8659fdffe0e5a
+msgid "Adding an Additional Guest Network"
+msgstr ""
+
+#: ../../networking/multiple_guest_networks.rst:47
+#: ../../networking/multiple_guest_networks.rst:97
+#: ../../networking/multiple_guest_networks.rst:135
+#: ../../networking/multiple_guest_networks.rst:153
+#: ../../networking/multiple_guest_networks.rst:173
+# fc94885acfb44c089b5b955040cda635
+# e90f66fa32fb4ac0bdd48def8833e52d
+# 443695bf438a4240b9c354d9c66f2292
+# dc150422f8d8498e81ccfa11cc7daf5f
+# f4162f2a3af54aee90b80a9efec6523f
+msgid "Log in to the CloudStack UI as an administrator or end user."
+msgstr ""
+
+#: ../../networking/multiple_guest_networks.rst:49
+#: ../../networking/multiple_guest_networks.rst:179
+# e9d2f3becfba421592c540e757fe27e8
+# 1e2cad5b28aa4f56bfee80c03c969d5c
+msgid "In the left navigation, choose Network."
+msgstr ""
+
+#: ../../networking/multiple_guest_networks.rst:51
+# 4e88ac1dcf2144278c13cac5cf518978
+msgid "Click Add guest network. Provide the following information:"
+msgstr ""
+
+#: ../../networking/multiple_guest_networks.rst:53
+# 752dce8be6894794b7f10719d33214c9
+msgid "**Name**: The name of the network. This will be user-visible."
+msgstr ""
+
+#: ../../networking/multiple_guest_networks.rst:55
+# 68d2d60b814f4b48805d73f511a0c3f4
+msgid "**Display Text**: The description of the network. This will be user-visible."
+msgstr ""
+
+#: ../../networking/multiple_guest_networks.rst:58
+# 2e28d86b3670448ea924597e1a6eafbb
+msgid "**Zone**. 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. The administrator must configure the IP range for each zone."
+msgstr ""
+
+#: ../../networking/multiple_guest_networks.rst:63
+# 783fa5ad4bb94a898e27fb2fb400ce30
+msgid "**Network offering**: If the administrator has configured multiple network offerings, select the one you want to use for this network."
+msgstr ""
+
+#: ../../networking/multiple_guest_networks.rst:67
+# e6d0251f520945198846d9589071d11c
+msgid "**Guest Gateway**: The gateway that the guests should use."
+msgstr ""
+
+#: ../../networking/multiple_guest_networks.rst:69
+# 82e7d212928549ba947dfe5e04919372
+msgid "**Guest Netmask**: The netmask in use on the subnet the guests will use."
+msgstr ""
+
+#: ../../networking/multiple_guest_networks.rst:72
+# 333d9595d92b4dbc9842d746d1dd8448
+msgid "Click Create."
+msgstr ""
+
+#: ../../networking/multiple_guest_networks.rst:76
+# cadd27c83ef84c9e9ce49c9ce9e5d8ca
+msgid "Reconfiguring Networks in VMs"
+msgstr ""
+
+#: ../../networking/multiple_guest_networks.rst:78
+# 38552d30397849ea975e0b5d28fd31a0
+msgid "CloudStack provides you the ability to move VMs between networks and reconfigure a VM's network. You can remove a VM from a network and add to a new network. You can also change the default network of a virtual machine. With this functionality, hybrid or traditional server loads can be accommodated with ease."
+msgstr ""
+
+#: ../../networking/multiple_guest_networks.rst:84
+# 205bea0ed92e4de594873aa8e5ad9d45
+msgid "This feature is supported on XenServer, VMware, and KVM hypervisors."
+msgstr ""
+
+#: ../../networking/multiple_guest_networks.rst:88
+# 7d8b8d41cfa04ea0b337a64b1206ae92
+msgid "Prerequisites"
+msgstr ""
+
+#: ../../networking/multiple_guest_networks.rst:90
+# bd4145a5e8ae4ca29cd7bdd5b1aab637
+msgid "Ensure that vm-tools are running on guest VMs for adding or removing networks to work on VMware hypervisor."
+msgstr ""
+
+#: ../../networking/multiple_guest_networks.rst:95
+# 42b8d9502ed54485bde4210b8fdbb499
+msgid "Adding a Network"
+msgstr ""
+
+#: ../../networking/multiple_guest_networks.rst:99
+#: ../../networking/multiple_guest_networks.rst:137
+#: ../../networking/multiple_guest_networks.rst:155
+# c398a820cb1648bc8799135cbaa74b1b
+# d48f631728b44c90be3cb811c9cd0505
+# 37c98038af7f4dc6a120b05e4e13c555
+msgid "In the left navigation, click Instances."
+msgstr ""
+
+#: ../../networking/multiple_guest_networks.rst:101
+#: ../../networking/multiple_guest_networks.rst:139
+#: ../../networking/multiple_guest_networks.rst:157
+# b25bff80ed07457f9b1f926c0a58cc6c
+# 39876863e78d47378acdd305a1e22606
+# 2f4e1895d207479597c89b7b137794df
+msgid "Choose the VM that you want to work with."
+msgstr ""
+
+#: ../../networking/multiple_guest_networks.rst:103
+#: ../../networking/multiple_guest_networks.rst:141
+#: ../../networking/multiple_guest_networks.rst:159
+# 00b5baacd9084cd580b5fc02a2eb93fb
+# cd7d2fceff8d47d5b392be059b471ab9
+# 3f13993fdab542d6b8318cc2fe353acb
+msgid "Click the NICs tab."
+msgstr ""
+
+#: ../../networking/multiple_guest_networks.rst:105
+# 47b1307c53ed41dfbe754e5141219451
+msgid "Click Add network to VM."
+msgstr ""
+
+#: ../../networking/multiple_guest_networks.rst:107
+# ebd8002977894bed935a5229f868dc66
+msgid "The Add network to VM dialog is displayed."
+msgstr ""
+
+#: ../../networking/multiple_guest_networks.rst:109
+# fa83b310f8904d8587c3dfdc52cacbad
+msgid "In the drop-down list, select the network that you would like to add this VM to."
+msgstr ""
+
+#: ../../networking/multiple_guest_networks.rst:112
+# dd48bfa27d7345aa87c6b7e63a358160
+msgid "A new NIC is added for this network. You can view the following details in the NICs page:"
+msgstr ""
+
+#: ../../networking/multiple_guest_networks.rst:115
+# 6463c065bc1943008470d1edad582974
+msgid "ID"
+msgstr ""
+
+#: ../../networking/multiple_guest_networks.rst:117
+# 9420ad95bce443da9b81765885249155
+msgid "Network Name"
+msgstr ""
+
+#: ../../networking/multiple_guest_networks.rst:119
+# f846a9f3d938451198081772cc74cb85
+msgid "Type"
+msgstr ""
+
+#: ../../networking/multiple_guest_networks.rst:121
+# 8592916e5acf4e70bafbdbda7c00c614
+msgid "IP Address"
+msgstr ""
+
+#: ../../networking/multiple_guest_networks.rst:123
+# c75427419ce04483b71df9bd261c2fbd
+msgid "Gateway"
+msgstr ""
+
+#: ../../networking/multiple_guest_networks.rst:125
+# d008ddbc8a054a27ae521d3e3b8a4013
+msgid "Netmask"
+msgstr ""
+
+#: ../../networking/multiple_guest_networks.rst:127
+# 41cff6439a0b42b5abab39913bc773bb
+msgid "Is default"
+msgstr ""
+
+#: ../../networking/multiple_guest_networks.rst:129
... 211783 lines suppressed ...